What’s (NOT) your killer feature?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

What’s (NOT) your killer feature?

Lovelady, Dennis E.
Well, since this came up, it got me thinking about “features”  that I wouldn’t miss if they’re not present in future version(s).  (I’m using, with no add-ons.)

First is hard to explain.  Situation is that we have an unpinned Data Grid displaying in TOAD, taking the bottom half of a window, with a long SQL statement partially hidden by that grid.  Now, when we use the cursor to try to select text from that SQL statement, the unpinned Data Grid will not move out of the way, and no scrolling takes place to let us see what’s being selected.  We have to interrupt the select operation, click on the Data Grid, then click on the SQL pane to make the unpinned pane go away… then we can select as normal.  This is worsened by the fact that the Data Grid will (almost, but not quite) always open when swapping between tabs.  I feel that an unpinned pane, once dismissed, should stay away until recalled intentionally.  And there should be a Dismiss capability that doesn’t involve gain/leave focus operation.  I also feel that it should not be possible for text to stay hidden while it’s being selected.  The text should scroll or the barriers should disappear.  (I hope that’s worded clearly enough.)

Second is that the Scope in the Find window seems to have a mind of its own.  I cannot count the number of times I’ve done a Replace All, only to find that All was not Replaced.  I check the Scope and it looks fine.  Nearest I can determine, Scope will revert to “Selected Text” at the will of the editor (perhaps related to data being selected - even if the data was selected by an error condition, and not by the user) - and then revert back!!!  These sorts of settings should Stick; that’s what the preferences are for.

Now maybe I’m misusing the application, or not exercising certain settings that I haven’t found, but these two issues have been the bane of my existence since I started using this tool.

Don’t get me wrong:  I absolutely love Toad and its capabilities, and I put up with these things because it’s worth the little pains along the way.  But it’d be much better without those pains, IMO.  Our organization is slow to change, and we’ll likely be on 10.6 for the next several years (perhaps until a notoriously warm place develops ice in its craters).  So not sure there is any help for it.

From: [hidden email] [mailto:[hidden email]] On Behalf Of Bert Scalzo
Sent: Thursday, July 26, 2012 7:34 AM
To: [hidden email]
Subject: RE: [toad] Whats your killer feature?

How about Toad 9.6 does not work with Oracle 11g case sensitive passwords – so user might not be able to connect ☺

From: [hidden email]<mailto:[hidden email]> [mailto:[hidden email]]<mailto:[mailto:[hidden email]]> On Behalf Of r_squires
Sent: Thursday, July 26, 2012 12:21 AM
To: [hidden email]<mailto:[hidden email]>
Subject: [toad] Whats your killer feature?

I was chatting with one of my colleagues who is still using TOAD 9.6 and I asked him why he didn't upgrade to 11.5. He wasn't sure what the benefit would be. We use the Schema Browser and SQL Editor primarily so the best I could come up with were:

1. The editor now highlights every instance of a selection
2. You can compare the values of multiple lines of data in the data grid to identify differences
3. Describing an object now groups all of your describes together so that you don't have lots of describe windows all over the place

But, it got me thinking. What's your killer feature?

<FONT size=2><BR>
DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email
in error, please notify us immediately and delete the email and any
attachments from your system. The recipient should check this email
and any attachments for the presence of viruses.  The company
accepts no liability for any damage caused by any virus transmitted
by this email.</FONT>