Re: JDBC behaviour - Mailing list pgsql-jdbc

From Sridhar N Bamandlapally
Subject Re: JDBC behaviour
Date
Msg-id CAGuFTBWrsMQBhrYkOUt3eNFE2RMd4Mpkzxg32ejjMFhqBwfb0Q@mail.gmail.com
Whole thread Raw
In response to Re: JDBC behaviour  (John R Pierce <pierce@hogranch.com>)
Responses Re: JDBC behaviour  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
Re: JDBC behaviour  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-jdbc
Andreas, ROLLBACK doesn't work as it do for all previous statements, 

autocommit ON is not option as it controlled by connection pool, 

with this the simple "statement" with need to replace with "try-catch", "savepoint", "statement" and "rollback to savepoint", this looks lot of changes in code to make it app/java-database compatible, 

still, this is bug



On Thu, Feb 18, 2016 at 3:22 PM, John R Pierce <pierce@hogranch.com> wrote:
On 2/18/2016 1:42 AM, Sridhar N Bamandlapally wrote:

but why?, this is not expected behavior

autocommit is just autocommit, its not responsible to treat multi-transactions as single or independent



its exactly how jdbc is defined to work,  fit into postgres's transaction model.

if autocommit is ON, then every statement is a standalone query.

if autocommit is OFF, then its in transaction mode.     JDBC has an implicit transaction start when you execute the first query, and you have to commit or rollback the transaction.


if you want each INSERT to run indepedently, then use autocommit ON.

--
john r pierce, recycling bits in santa cruz



--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

pgsql-jdbc by date:

Previous
From: John R Pierce
Date:
Subject: Re: JDBC behaviour
Next
From: Vladimir Sitnikov
Date:
Subject: Re: JDBC behaviour