Re: JDBC behaviour

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: JDBC behaviour
Date: 2016-02-18 09:52:45
Message-ID: 56C5946D.4070904@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sridhar N Bamandlapally 2016-02-18 10:02:20 Re: JDBC behaviour
Previous Message Andreas Joseph Krogh 2016-02-18 09:46:12 Re: JDBC behaviour

Browse pgsql-hackers by date

  From Date Subject
Next Message Sridhar N Bamandlapally 2016-02-18 10:02:20 Re: JDBC behaviour
Previous Message Andreas Joseph Krogh 2016-02-18 09:46:12 Re: JDBC behaviour

Browse pgsql-jdbc by date

  From Date Subject
Next Message Sridhar N Bamandlapally 2016-02-18 10:02:20 Re: JDBC behaviour
Previous Message Andreas Joseph Krogh 2016-02-18 09:46:12 Re: JDBC behaviour