Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: JDBC feature request: auto savepoint per command
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-jdbc(at)postgreSQL(dot)org
- Subject: Re: JDBC feature request: auto savepoint per command
- Date: Tue, 24 Apr 2007 14:26:33 -0400 (EDT)
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
- Follow-Ups:
- Re: JDBC feature request: auto savepoint per command
- From: Tom Lane
- Re: JDBC feature request: auto savepoint per command
- References:
- JDBC feature request: auto savepoint per command
- From: Tom Lane
- JDBC feature request: auto savepoint per command
- Prev by Date: Re: Can't build postgresql-jdbc-8.2-505 on Fedora 7
- Next by Date: Re: JDBC feature request: auto savepoint per command
- Previous by thread: Re: JDBC feature request: auto savepoint per command
- Next by thread: Re: JDBC feature request: auto savepoint per command
- Indexes: