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

Re: Connection.setReadOnly()

From: Kris Jurka <books(at)ejurka(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 00:23:44
Message-ID: alpine.BSO.2.00.0912101922140.16299@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Thu, 10 Dec 2009, John R Pierce wrote:

> Kris Jurka wrote:
>> Just because your connection is readonly doesn't mean that everyone elses 
>> is as well.  If you want a consistent view of the database you can get that 
>> with a serializable transaction.
>
> my oracle developers are screaming bloody murder over this.
>
> they have processes that do nothing but reads.   jdbc tosses a BEGIN; out 
> automatically.   these processes never Commit(); on a read, why should they?

So if they go to the trouble of doing a setReadOnly call, why not simply 
do a setAutoCommit(true) call as well?

Kris Jurka

In response to

Responses

pgsql-jdbc by date

Next:From: John R PierceDate: 2009-12-11 00:33:46
Subject: Re: Connection.setReadOnly()
Previous:From: John R PierceDate: 2009-12-11 00:19:49
Subject: Re: Connection.setReadOnly()

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