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