Re: Confusion regarding autocommit - Mailing list pgsql-jdbc

From Mark Rotteveel
Subject Re: Confusion regarding autocommit
Date
Msg-id 3c49b9c9-6fd1-9b52-3007-999041551960@lawinegevaar.nl
Whole thread Raw
In response to Confusion regarding autocommit  (siddharth yanamandra <yanamandra.siddharth@gmail.com>)
List pgsql-jdbc
On 10-4-2019 11:09, siddharth yanamandra wrote:
> Hi
> 
> We have an application which used the jdbc 8.2-504 version. We have 
> recently tried to update it to 42.2.5 jre 7 version. During this update 
> we faced the issue "could not commit when autocommit is enabled" error 
> so we have decided to assign false to autocommit during connection 
> initiation. Now many of the SQL statements we use are select statements 
> and we have read from many sources that even select statements should be 
> committed to clear locks on tables. Is this necessary or is it ok to 
> just close the connection after the operations are done(for select 
> statements only).

The point of auto-commit mode is that this happens automatically. You 
should not call commit() or rollback() when using auto-commit. If you 
want to explicitly call commit or rollback, then you should disable 
auto-commit using setAutoCommit(false).

Mark
-- 
Mark Rotteveel



pgsql-jdbc by date:

Previous
From: siddharth yanamandra
Date:
Subject: Confusion regarding autocommit
Next
From: Mark Rotteveel
Date:
Subject: Re: ResultSet.getObject(..., LocalTime.class) not working withPostgres timetz type