Re: Is statement.executeBacth() a transaction?
- From: Lew <noone@xxxxxxxxxxxxx>
- Date: Fri, 31 Oct 2008 06:35:29 -0400
George wrote:
Thank you. As always, I got a bit more confused on the other by
clearing up one part. I originally thought all the statements in one
transaction are all executed or non executed in jdbc automatically. Am
I right? However, the second last paragraph in the article I linked
seems to say the opposite. It says one needs to rollback when
SQLExcption is thrown, which seems to indicate that one transaction
(one conn.commit()) might leave some statement executed and some
not.
Please do not top-post. (nor strictly bottom-post - correct is to post inline, trimming no-longer relevant content.)
That same article points out that all statements in a transaction are committed or rolled back together. That is, after all, the entire point of transactions.
"Seems to indicate" is a different proposition from "does indicate".
--
Lew
.
- Follow-Ups:
- Re: Is statement.executeBacth() a transaction?
- From: George
- Re: Is statement.executeBacth() a transaction?
- References:
- Is statement.executeBacth() a transaction?
- From: George
- Re: Is statement.executeBacth() a transaction?
- From: Lew
- Re: Is statement.executeBacth() a transaction?
- From: George
- Re: Is statement.executeBacth() a transaction?
- From: Lew
- Re: Is statement.executeBacth() a transaction?
- From: George
- Is statement.executeBacth() a transaction?
- Prev by Date: Re: Redundant GPS data
- Next by Date: Re: How to set the compiler to handle thousand loops ?
- Previous by thread: Re: Is statement.executeBacth() a transaction?
- Next by thread: Re: Is statement.executeBacth() a transaction?
- Index(es):
Relevant Pages
|