| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Portals and nested transactions |
| Date: | 2004-07-14 21:56:36 |
| Message-ID: | 40F5AC14.1030500@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> On the other hand, some people supported the idea that v3 Bind portals
> should behave nontransactionally, while DECLARE portals should behave
> transactionally. Maybe we could make that a property of the portal, or
> even a user-selectable property (where we would define a reasonable
> default behavior).
If this is going to happen, either the protocol-level portals need
access to all the functionality of DECLARE, or it needs to be done as a
user-selectable property of DECLARE. Currently the JDBC driver uses only
protocol-level portals, but as soon as we want to support large
scrollable or holdable ResultSets (effectively unsupported by the
current driver) it will have to use DECLARE to get access to SCROLL /
WITH HOLD.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2004-07-14 22:19:23 | Re: Another locale test program |
| Previous Message | Oliver Jowett | 2004-07-14 21:52:35 | Re: Portals and nested transactions |