Re: JDBC feature request: auto savepoint per command - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: JDBC feature request: auto savepoint per command
Date
Msg-id Pine.BSO.4.64.0704231515230.22670@leary.csoft.net
Whole thread Raw
In response to JDBC feature request: auto savepoint per command  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: JDBC feature request: auto savepoint per command  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc

On Mon, 23 Apr 2007, Tom Lane wrote:

> Can anyone see a solution for this in the context of the existing driver
> facilities?  If not, is it reasonable to ask for a driver option to do
> auto-savepointing?  There is already an equivalent facility in psql, so
> the idea doesn't seem unreasonable to me.
>

Previous discussions on this topic had the idea that auto-savepointing
would be done on a per-connection basis enabled via a URL parameter or
DataSource option.  In an application server would you have a separate
connection pool for auto-savepointing connections?  Would you force all
transactions to use auto-savepoints even if they didn't want/need them?
You could enable/disable it dynamically, but that would require pg
specific code, is that what they want to do?

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Can't build postgresql-jdbc-8.2-505 on Fedora 7
Next
From: Tom Lane
Date:
Subject: Re: JDBC feature request: auto savepoint per command