RE: How do I set <ctrl>+Enter back to Execute Snippet?

Arrrr! You beat me to it!

I'll add that you should look at the SQL in the Edit SQL dialog. Has it been modified in any way (other than formatting)? If so, what are the modifications? Are they correct?

The feature compares unknown identifiers to a long list of built-in routines so that items like TO_CHAR, SYSDATE, etc. are not converted into a bind unexpectedly. If your statement is using a built-in that is being converted into a bind, please pass it on and I'll update the list.

It also changes references to your own functions into bind variables and comments out the original call so you can reinstate it if desired. In some cases function calls may be inaccessible from outside of a package, or in other cases the function modifies data which would be undesirable when just testing the standalone SQL. In other cases you may want the function call to get an accurate plan. Without being able to anticipate all needs I've opted for the safe approach of commenting out function calls and leaving the original commented.

Michael

From: [email protected] [mailto:[email protected]] On Behalf Of SCHROEDER, NATHAN E (AG/1000)
Sent: Friday, July 20, 2012 1:53 PM
To: [email protected]
Subject: RE: [toad] How do I set <ctrl>+Enter back to Execute Snippet?




Arrr! That be no bug, me lads and lassies, that be a feature!

If you’re executing a SQL statement in the context of what Toad sees as PL/SQL, it tries to scan the SQL for bind variables, then scan the rest of the code to find the values for those variables and substitute them in. It then presents the result to you to confirm that it got it right (or correct it), and then it will execute the SQL.

Nate Schroeder
Enterprise Services - Data Management Team
Monsanto Company
800 N. Lindbergh Blvd. B2SB - Saint Louis, MO - 63167
314-694-2592

From: [email protected] [mailto:[email protected]] On Behalf Of Janel Hansen
Sent: Friday, July 20, 2012 12:21 PM
To: [email protected]
Subject: [toad] How do I set <ctrl>+Enter back to Execute Snippet?

Hi everyone,

OK…I always, always, always hit <ctrl>+Enter to execute SQL.  All of a sudden today I try it and it’s opening up a pop-up editor window?  Does anyone know how I can get rid of this annoyance?

I’m on version 11.5.0.56.  I went to a Schema Browser to view a Package.  I double-clicked the package to open up the code in an editor window.  I am then trying to run a specific piece of SQL in the package…something I do very often.  It now pops up what looks to be an Edit SQL window.  How do I set this back?  I looked in Toad Options>Editor>Behavior>Key-Mapping, but I don’t even see where this is set anywhere in there.  I also looked at Toolbars/Menus>Shortcuts, but I didn’t see <ctrl>+Enter set there either.  I did try resetting the shortcut to it here for Editor>Execute Snippet, opened a new Editor, but still doesn’t work. (opens the pop-up)

Any help would be much appreciated.  Thanks!
Janel

This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled
to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and
all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its
subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware".
Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying
this e-mail or any attachment.

The information contained in this email may be subject to the export control laws and regulations of the United States, potentially
including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of
Treasury, Office of Foreign Asset Controls (OFAC).  As a recipient of this information you are obligated to comply with all
applicable U.S. export laws and regulations.