Murphy’s Law: Anything that can go wrong, will!
Corollary to Murphy’s Law: Murphy was an optimist.
Tobi
Murphy’s Law: Anything that can go wrong, will!
Corollary to Murphy’s Law: Murphy was an optimist.
Tobi
Never having been a DBA I can't say. It's only the poor programmers who are
treated like brick layers, DBA's are held in awe, and in the utmost regard.
Having been an operator, programmer, systems analyst, system admin, DBA, and
most things in between, I can say that yes, we DBAs should be held in
awwwww.
Wait...
Rich -- [TeamT]
Disclaimer: If you're in IT for recognition, you're in the wrong business.
That’s why it’s best to not be a “poor” programmer, but
an exceptional one.
Hi Rich,
Disclaimer: If you're in IT for recognition, you're in the
wrong business.
I don't know, TeamT are pretty famous - aren't they?
Cheers,
Norm. [TeamT]
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
In my opinion, the solution to this should be to disable incremental search in
the live data grids. I don’t think we ever had that in previous versions.
We’d be fighting the grid’s “natural” behavior if we
tried to keep incremental search enabled, but didn’t allow it to fetch.
Think about this scenario: If we have incremental search, but it does not fetch
any extra rows, and someone uses it but finds no result, they’ll think
(wrongly) “ok, I guess there are no rows with that value”.
Live dataset filtering can only be done properly when all rows are fetched.
Better to use a change to the where clause, IMHO.
Hmm….maybe the best solution is to keep incremental search and column
drag-grouping disabled UNTIL all rows are fetched. That way, you can still have
it, and you are in control of the fetch.
Or a warning, ‘more rows to be fetched, wanna get some more?’
The group by’s force all the rows back, maybe the search should too.
Heh, perhaps I should join the Beta then *{ - although installing software from t’internet is frowned upon where I work (and I quite like my job!). I wonder how many of the beta users are able to use it for day-to-day work?
We don’t have that option. I opened a case with our grid vendor trying to
get that done. It’s not going to happen.
Jeff writes:
Or a warning, 'more rows to be fetched, wanna get some more?'
Different architecture, but Toad for SQueaL Server does something like that.
Which reminds me, I need to go check on my SS DBs...[sigh]
Rich -- [TeamT]
Disclaimer: http://www.orcldba.com/ace/2008/08/05/daydreams/
For what it’s worth, I doubt I’d ever use the new column grouping functionality, and wouldn’t ever need to use the search facility (which only goes on the first char(s) of the cells anyway), so I’d prefer to have an option that switches said search facility off.
I can see that the column grouping might be useful if you’re an analyst, etc who doesn’t know much about SQL, but I prefer to have greater control over how I query my tables! However, the search facility just seems … pointless - it’s not intuitive (especially when compared to previous versions of Toad), and the filter (or, in the case of the editor, the where clause as you mentioned) gives you greater flexibility anyway!
I personally as well would see usefulness of such feature just in end user applications where there are provided 2-3 screens of data.
but definitely not in grids browsing database tables.
except of that, there is already for some time function “Find data” in context menu that provides basically the same functionality and can be invoked by purpose, considering all the consequences.
emha.
Heh, perhaps I should join the Beta then *{
- although installing
software from t'internet is frowned upon where I work (and I quite like my
job!). I wonder how many of the beta users are able to use it for day-to-day
work?
Join us! You know you want to...
As far as using the beta for day-to-day, it depends. It is a beta after
all. I tend to use it on development databases...Just In Case.
Right now, we're betaless. That's a Good Thing. But Mark says the next
beta cycle will be starting soon enough.
Toad Beta is a wonderful thing! Like this Toad list, one has direct access
to the Toad Dev Team. And they actually listen! Of course, not
everything everyone wants can be implemented (see also "chaos"), but it's
great to know that We, The Customers, have direct input/feedback on future
Toads.
BTW, I download all my software from home. In my case, my internet
connection is faster there...
Enjoy!
Rich -- [TeamT]
Disclaimer: I like typing "".
As being a beta user, most of the time I use the beta for production work.
Sometimes I must go back to the GA version because there are things introduced
that makes it impossible to work. Not often.
Report the problem in the forum and the developers and othersare listening to
your ideas and problems. Sometimes there are workarounds or better procedures
and sometimes it is an bug. When an update for the beta is there, and there are
updates every week, retry the procedure and proceed with all the new options
that are available.
Groetjes,
Wim
On Thu, Oct 29, 2009 at 15:03, boneist1 wrote:
Heh, perhaps I should join the Beta then *{;-) - although installing
software from t'internet is frowned upon where I work (and I quite like
my job!). I wonder how many of the beta users are able to use it for
day-to-day work?
I can say that yes, we DBAs should be held in awwwww
Wait...
LOL, that was nicely subtle
RAS
I don’t see Ed’s post, but incremental search is disabled in the live data grids. If you start typing in an editable live grid then the cell contents will change just as in Toad 9.7 without requiring that you first press ENTER or any other key to enter edit mode.
Michael
I meant to add that this change is for 10.2 and for a second patch that we plan on delivering in December.
Michael
What about in a non-editable live grid? (I assume that’s what a grid returned in the editor would count as)
Is the functionality to click in a cell and be able to select part of the contents (for C&P purposes) no longer going to be available?
What about in a non-editable live grid? (I assume that's what a grid returned in the editor would count as)
In non-editable live grids typing with a selected cell will do nothing just like in 9.7.
Is the functionality to click in a cell and be able to select part of the contents (for C&P purposes) no longer going to be available?
One thing at a time. Working on that one next.
Michael
One thing at a time.
Working on that one next.
aah, thanks; I thought it had been sorted already but not mentioned! I shall try to curb my impatience *{