Re: [GENERAL] Problem JDBC, AutoCommit ON and SELECT FOR UPDATE

2015-03-06 Thread Thomas Kellerer
Philippe EMERIAUD wrote on 06.03.2015 17:27: Hi all, We have an application based on DB2 database, We are testing this same application on PostgreSQL database. By default we are in autocommit on mode. On DB2 (and Oracle), the query SELECT FOR UPDATE locks the row until the resultset is closed.

Re: [GENERAL] Problem JDBC, AutoCommit ON and SELECT FOR UPDATE

2015-03-06 Thread Dave Cramer
Can you point me to the source of that quote ? The documentation here http://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html does not specify anything about ResultSet closing, or completion ? Short version is that the driver does not hold the lock past the return of the result set, so

Re: [GENERAL] Problem JDBC, AutoCommit ON and SELECT FOR UPDATE

2015-03-06 Thread Adrian Klaver
On 03/06/2015 08:27 AM, Philippe EMERIAUD wrote: Hi all, We have an application based on DB2 database, We are testing this same application on PostgreSQL database. By default we are in autocommit on mode. On DB2 (and Oracle), the query SELECT FOR UPDATE locks the row until the resultset is closed

[GENERAL] Problem JDBC, AutoCommit ON and SELECT FOR UPDATE

2015-03-06 Thread Philippe EMERIAUD
Hi all, We have an application based on DB2 database, We are testing this same application on PostgreSQL database. By default we are in autocommit on mode. On DB2 (and Oracle), the query SELECT FOR UPDATE locks the row until the resultset is closed. On PostgreSQL database (all versions) this sam