On Thu, 8 Jan 1998, Herouth Maoz wrote:
> At 18:05 +0200 on 7/1/98, Peter T Mount wrote:
>
>
> > PS: in the current implementation, con.setAutoCommit(false) itself
> > initiates the transaction, not the next sql call.
>
> Ah, good of you to reveal this! This would mean that I would have to call
> it again if I want another transaction to start after I've committed the
> first.
Not the case. Once you have setAutoCommit(false), calling commit()
automatically begins a new transaction. The same goes for rollback().
--
Peter T Mount petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk