Re: JDBC behaviour - Mailing list pgsql-jdbc

From Sridhar N Bamandlapally
Subject Re: JDBC behaviour
Date
Msg-id CAGuFTBXf_1Vws=Ja3nCqvRGvWPE2W4ATpCyxrreCgWFi0Yii=w@mail.gmail.com
Whole thread Raw
In response to Re: JDBC behaviour  (Andreas Joseph Krogh <andreas@visena.com>)
Responses Re: JDBC behaviour
Re: JDBC behaviour
List pgsql-jdbc
setAutoCommit(false), it should not be treating all next transactions as single set, simple, this is what expected behavior

 

On Thu, Feb 18, 2016 at 2:34 PM, Andreas Joseph Krogh <andreas@visena.com> wrote:
På torsdag 18. februar 2016 kl. 09:51:47, skrev Sridhar N Bamandlapally <sridhar.bn1@gmail.com>:
Ok, let me put this way
 
in JDBC we have setAutoCommit( false ) , and all dmls are independent transactions
 
and when any transaction fails then the session not allowing next transactions
 
in Java when we do setAutoCommit( false ) its behaving like all transactions in BEGIN-END block, this is not expected behavior
 
i guess this is bug
 
No, you got it backwards. With autocommit=false all statements are NOT independent transactions.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 

Attachment

pgsql-jdbc by date:

Previous
From: Andreas Joseph Krogh
Date:
Subject: Re: JDBC behaviour
Next
From: Vladimir Sitnikov
Date:
Subject: Re: JDBC behaviour