You should use the driver's set autocommit(false) instead, as then the
driver will know the state of the connection.
BTW, I'm sure oracle has a similiar "begin" statement.
On Mon, 2004-03-08 at 06:40, Harry Mantheakis wrote:
> I ported a relatively simple application using Oracle 8i with a JDBC client
> to PostgreSQL 7.4 with the same JDBC client, and everything just worked!
> One thing that did come to light was that PG offers a proprietary 'BEGIN'
> statement as a means of controlling transactions.
> With Oracle, I was used to setting auto-commit to false at the start of a
> transaction, and then calling commit or rollback at the end.
> Is it safe for me to continue setting auto-commit to false for transactions,
> and are there any compelling reasons - significant performance gains,
> perhaps - why I might want to consider adopting PG's 'BEGIN' statement
> Many thanks in anticipation.
> Harry Mantheakis
> London, UK
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
519 939 0336
ICQ # 14675561
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2004-03-08 13:31:42|
|Subject: Re: Using auto-commit OFF for transactions - instead of|
|Previous:||From: Harry Mantheakis||Date: 2004-03-08 11:40:18|
|Subject: Using auto-commit OFF for transactions - instead of BEGIN|