Re: JDBC behaviour - Mailing list pgsql-jdbc

From Craig Ringer
Subject Re: JDBC behaviour
Date
Msg-id CAMsr+YEwDDCWgKFm2V1G5-sWY_P6MYiTLWs=z6fW1y0w50zyjg@mail.gmail.com
Whole thread Raw
In response to Re: JDBC behaviour  (Sridhar N Bamandlapally <sridhar.bn1@gmail.com>)
List pgsql-jdbc
On 23 February 2016 at 12:06, Sridhar N Bamandlapally <sridhar.bn1@gmail.com> wrote:

I mean, we will not change existing functionality/behavior/code as there may be dependency applications with same behavior


What you need to do is help test and review the patch that you've already been sent links to. It will add a connection option that you can use to control whether or not the driver does automatic savepoints. So you won't have to change application code so long as the application gives you a way to specify options in the JDBC URL or Properties dictionary. At least, not because of that.

Go look at https://github.com/pgjdbc/pgjdbc/pull/477 . If you really want to make progress, take that patch and add support for a JDBC URL connection option  then send a new pull request. With unit tests.

I am confident that automatic SAVEPOINTs are the *only* way you will get the behaviour you want with PostgreSQL and PgJDBC.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: JDBC behaviour
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] JDBC behaviour