Re: Is statement.executeBacth() a transaction?

Lew wrote:
Did you read my answer that you quoted?

George wrote:
Well, it seems that either I did not get your explanation or you did
not make it clear enough. I appreciate your time and effort in the
usenet, but it does not help by sentences as this.

Well, I'm sorry it doesn't help you, but repeating my answer as a
question leaves me with the conclusion that you didn't read the
answer.

Lew:
If you set auto-commit to 'false', nothing happens automatically.
That is the whole point of setting auto-commit to 'false'.

George:
In my example above, I did set autocommit to false and use the

Then you must EXPLICITLY (to quote your shouting) call either
'commit()' or 'rollback()' to end the transaction.

commit() explicitly.  The question is that, in case first update runs
fine and SQLException is thrown for the second "update", will the jdbc
automatically rollback to the situation before the transaction,

Question answered upthread.

(meaning rollback/wipe-out the first update), or should I do it
manually in the catch by calling rollback()?  I do not think either
your post or the article gives a clear answer for this or maybe I just
missed the point somewhere.

I said:
You have to explicitly call either 'commit()' or 'rollback()' to
terminate the transaction.

You asked:
do I still need to EXPLICITLY have rollback() in the catch{} ...?

You repeated the answer almost word for word only with a question
mark.

You have to explicitly call either 'commit()' or 'rollback()' to end
the transaction.

I do not know how to make that clearer. I do not comprehend repeating
the answer with a question mark as a legitimate question. If you turn
off auto-commit, then you have to use either 'commit()' or
'rollback()' explicitly. It doesn't necessarily have to be in the
'catch' block, but it has to happen somewhere.

--
Lew

.

Relevant Pages

  • Re: Using Transaction scope
    ... If a connection is timeout and the transaction has been ... SQL Server will automatically rollback the ... side since it cannot receive the commit command from the client. ...
    (microsoft.public.sqlserver.clients)
  • Re: Exception handling in Triggers.
    ... > So if you open up QA do transaction mock statement, ... > The reason why this is important is that a rollback as you ... > SQL Server will automatically rollback transactions if the ... >>ben brugman. ...
    (microsoft.public.sqlserver.server)
  • Exception handling in Triggers.
    ... If we can get away from the trigger for a second. ... So if you open up QA do transaction mock statement, ... The reason why this is important is that a rollback as you ... SQL Server will automatically rollback transactions if the ...
    (microsoft.public.sqlserver.server)
  • Creating a repeating section
    ... The fields are name, address, transaction date, ... transaction amount. ... I want to create a statement for the customer with their ... repeating section. ...
    (microsoft.public.word.mailmerge.fields)