Skip site navigation (1) Skip section navigation (2)

Re: Connection.setReadOnly()

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Connection.setReadOnly()
Date: 2009-12-11 01:16:38
Message-ID: 4B219D76.1080600@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
John R Pierce wrote:
> Oliver Jowett wrote:

>> If your oracle developers don't want manually committed transactions,
>> perhaps they should.. turn on autocommit.
>>   
> 
> otherwise, an app thats doing purely read queries has to periodically
> issue a Commit().   I have to say, doing Commit() on read operations is
> NOT at all intuitive.

Maybe not, but it's a fairly well known quirk of Postgresql that
long-running transactions don't work so well; the JDBC driver is no
different to any other interface in this regard.

If you don't care about transaction boundaries, why are you even turning
off autocommit in the first place? It's a little unfair to explicitly
turn off autocommit, then complain that you need to manually commit
transactions!

-O

In response to

Responses

pgsql-jdbc by date

Next:From: Oliver JowettDate: 2009-12-11 01:26:06
Subject: Re: Connection.setReadOnly()
Previous:From: John R PierceDate: 2009-12-11 00:57:08
Subject: Re: Connection.setReadOnly()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group