Commits

Toad for Oracle
1

Can anyone tell me why when INSERTS or UPDATES are done in TOAD and then COMMIT
is executed that they system would ask you to COMMIT or ROLLBACK when you then
quit TOAD?

We have a suspicion here that we need to close TOAD to have our COMMITS
commited.

–
Daniel E. Hofford HHCS
www.hoofnexus.com
equsnarnd@gmail.com
“Our gold does not chink and glitter. It gleams in the sun and neighs in the
dark.” Chief Joseph
“To practice equestrian art is to establish a conversation on a higher level
with the horse; a dialogue of courtesy and finesse.” Nuno Olivera, Reflections
on Equestrian Art
“Happiness is a decision you make and a commitment you keep, not something that
just happens to you.” Daniel Hofford

2

Are you selecting through DB Links after your commit? That would cause Oracle to
start a new transaction, and Toad to prompt for commit when it is closing.

3

Do you mean are any SELECTS done? Sure. But why would a SELECT require a
COMMIT or ROLLBACK?

On Thu, Oct 15, 2009 at 12:07 PM, John Dorlon wrote:

Are you selecting through DB Links after your commit?    That would cause
Oracle to start a new transaction, and Toad to prompt for commit when it is
closing.
4

Any transaction - including selects - across a database link would cause
Oracle to view it as an open transaction. In other words: it’s not Toad
telling you that there is un-commited transactions, it’s the Oracle
database.

Roger S.