“Dump specified” predates threaded dumps. It allows you do do a partial dump (perhaps the current year if you have a date field indexed) or, pre -thread, break the data into groups
Ron,
Are you thinking of “dump specified” where you supply the range for each “thread”? That’s a very different beast from using the -threads proutil option.
The threaded dump can be very effective but, as George mentions, it will depend on your indexes. And you might benefit from doing an idxcompact first to clean up your post purge situation.
Sure. On the other hand you could use some cue other than a scroll bar to tell the user that there is something out there.
For instance, it is possible to have a fill-in that is wider than the available space. And in a character screen you probably don't want to be drawing boxes around that and...
There are frame attributes such as "scrollable" and "scrollbar-horizontal" that allow you to control scroll bars.
As for frames that are wider than the screen... sometimes that's useful. ProTop has a couple of panels that are much, much wider than even the standard ProTop screen of 160 columns...
"Useful" is in the eye of the beholder...
If the sorts of things that you are developing and whatever framework you are using make use of it then it might be useful.
But an awful lot of frameworks ignore it.
Well, yes. But since that has not happened yet I am suspicious that the malware known as "anti-virus" may be doing something to interfere with the proper operation of the code.
"Servers" do not typically make GUI requests. That would be something that, presumably, is handled on the client where the (G)UI is running.
I don't know what you mean by that. "As we know" seems to suggest that you already know. And, yet, you are asking a question about how to do it. So I'm a...
Your report timestamp precision is only to the second. I don’t know if that is because the data captured is only precise to the second or if it is just being truncated. But if the underlying data is a datetime field you could get millisecond precision and would likely see some sort of “gaps”...
Locking someone out after failed login attempts does not prevent additional *attempts*.
To do that you would need to teleport to the perpetrators location and handcuff them before than can start to try to login again.
Of course there could also be a gang of people trying to sneak in from...
After you fail 5 times you are “locked out”, right? Meaning that even if someone continues guessing (another 15 times) and happens to guess correctly they still don’t get in. But the attempts are noted. Which you would want.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.