RE: RE: Commit Question

Just replied to Gregory.

 

It is not the case.

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of
SCHROEDER, NATHAN E (AG/1000)
Sent: Friday, October 28, 2011 11:14 AM
To: [email protected]
Cc: Leo Korin
Subject: [toad] RE: Commit Question

 

  

I'll bet it's a session issue.  He probably has "run scripts in separate
session" or whatever that option is called set, so F5 and Run As Script
do the commit in a different session, and so don't commit the work from
the session in which he did the work.

 

Nate Schroeder

Enterprise Services - Data Management Team

Monsanto Company

800 N. Lindbergh Blvd. LC4D - Saint Louis, MO - 63167

314-694-2592

 

From: [email protected] [mailto:[email protected]] On Behalf Of
Leo Drobnis
Sent: Friday, October 28, 2011 10:11 AM
To: [email protected]
Cc: Leo Korin
Subject: [toad] Commit Question

 

A co-worker of mine puzzled me a bit.

 

He installed TOAD 11.0.0.116.  When he runs a commit (typed in the
editor) and uses either F5 or execute as script, the commit does not
actually commit into the DB, even thought the committed message shows up
in TOAD.  When F9 or execute statement is clicked, commit works fine.

 

According to him, TOAD 10.6.0.42 worked just fine.  The actual commit
button works as well.

 

Below is the spooled SQL.

 

I am very curious as to what is going on.

 

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.