Re: Is statement.executeBacth() a transaction?
- From: Lew <lew@xxxxxxxxxxxxx>
- Date: Fri, 31 Oct 2008 11:32:24 -0700 (PDT)
Lew wrote:
You have to explicitly call either 'commit()' or 'rollback()' to
terminate the transaction.
George <zgg...@xxxxxxxxx> wrote:
So if I have the commint() [sic] as in the above example, do I still need to
It's 'commit()', not 'commint()'.
EXPLICITLY have rollback() in the catch{}, or the library will call
roll back in case of any problems automatically?
Did you read my answer that you quoted?
If you set auto-commit to 'false', nothing happens automatically.
That is the whole point of setting auto-commit to 'false'.
Did you read the tutorial that you cited?
--
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
- 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: 7.0 wishlist?
- Next by Date: Re: Why we should (not?) have closures after all
- Previous by thread: Re: Is statement.executeBacth() a transaction?
- Next by thread: Re: Is statement.executeBacth() a transaction?
- Index(es):