Re: JDBC3 + HOLD_CURSORS_OVER_COMMIT

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC3 + HOLD_CURSORS_OVER_COMMIT
Date: 2004-07-20 21:53:07
Message-ID: 40FD9443.7000301@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Peter Eisentraut wrote:
> Oliver Jowett wrote:
>
>>It occurred to me that we can support JDBC3's
>>HOLD_CURSORS_OVER_COMMIT behaviour quite simply by doing the same
>>thing we do with scrollable resultsets -- disable use of cursors
>>entirely.
>>
>>Does this sound worth doing? Obviously we could replace it with
>>proper WITH HOLD cursor-backed resultsets eventually..
>
>
> PostgreSQL 7.4 supports holdable cursors.

Yes, but the JDBC driver doesn't have the necessary logic to use them --
it always uses V3 protocol-level portals which can't be made WITH HOLD.

Disabling cursor use when the JDBC app wants a holdable cursor is a
small change. Adding support for cursors via DECLARE is a big change.

(also see my soon-to-be-sent message about V3 + DECLARE -- using DECLARE
looks like it's not an option for us currently)

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2004-07-20 22:09:49 V3 protocol + DECLARE problems
Previous Message Peter Eisentraut 2004-07-20 21:49:13 Re: JDBC3 + HOLD_CURSORS_OVER_COMMIT