| From: | Peter T Mount <pgint(at)maidast(dot)demon(dot)co(dot)uk> |
|---|---|
| To: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: [INTERFACES] Re: JDBC transactions |
| Date: | 1998-01-08 12:59:34 |
| Message-ID: | Pine.LNX.3.95.980108125719.7637A-100000@maidast |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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(at)earthling(dot)net or pmount(at)maidast(dot)demon(dot)co(dot)uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter(at)maidstone(dot)gov(dot)uk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glynn Black | 1998-01-08 13:16:56 | |
| Previous Message | Herouth Maoz | 1998-01-07 22:40:46 | Re: JDBC transactions |