Hi folks,
I was pretty used to just kicking scripts off in sqlplus with one button click.
However, 10.6.0.42 requires me to save the editor window before running sqlplus.
Is this a feature or a bug? It does the same thing for the quest script runner.
Cheers,
Paul
This email was scanned by MessageLabs
Just click “No” to the save prompt and it will pass the Editor
contents. The change came as a result of a support case, but it also is more
consistent with the other areas where SQL is sent off to external sources.
The support case was as follows…
Load a script which calls another script in the same folder. It uses
@Filename.sql instead of @FullPath\Filename.sql.
Modify the script, do not save it.
Send to SQL*Plus from the Editor.
The referenced script will not execute if the current working directory is
not the full path of Filename.sql. The current working directory will change
if you load a file from elsewhere in Toad for example so it’s pretty
easy for the current working directory to change unknowingly behind the
scenes.
The current behavior gives you the opportunity to save if desired, cancel the
execution request, or not save and send the Editor contents. It’s an extra
click in your case, but should support all expected outcomes where 10.5 was
limited.
Michael
Sounds to me that this behaviour should be under a setting. I did not have this
yet, but it sounds not good to me. I already pushed a button to run the script,
now I must make a decision too?
del .
are you sure?
No
Why are you uncertain?
Groetjes,
Wim
On Tue, Sep 21, 2010 at 19:27, Michael Staszewski
wrote:
Just click “No” to the save prompt and it will pass the Editor contents.
The change came as a result of a support case, but it also is more
consistent with the other areas where SQL is sent off to external sources.
The support case was as follows…
Load a script which calls another script in the same folder. It uses
@Filename.sql instead of @FullPath\Filename.sql.
Modify the script, do not save it.
Send to SQL*Plus from the Editor.
The referenced script will not execute if the current working directory
is not the full path of Filename.sql. The current working directory will
change if you load a file from elsewhere in Toad for example so it’s
pretty easy for the current working directory to change unknowingly
behind the scenes.
The current behavior gives you the opportunity to save if desired, cancel
the execution request, or not save and send the Editor contents. It’s an
extra click in your case, but should support all expected outcomes where
10.5 was limited.
Michael
Morning Wim,
del .
are you sure?
No
Why are you uncertain?
I once did:
cd oracle_home_I_Want_to_delete
rm -Rf *
I could have done with a prompt then! The cd failed and I proceeded to
wipe out a number of Oracle homes I didn't want to delete. I like this
better:
cd oracle_home_I_Want_to_delete && rm -Rf *
or
rm -Rfi *
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