| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | fschmidt <fschmidt(at)gmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: setFetchSize |
| Date: | 2011-10-26 06:31:26 |
| Message-ID: | CA+0W9LOecXBWAW83WZNqG=BWYfpr0dnXYpa+n34RqZhHcKPjUw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 26 October 2011 19:09, fschmidt <fschmidt(at)gmail(dot)com> wrote:
> But looking at the JDBC code, the main use I see of portals is for
> setFetchSize(). And setFetchSize() is badly crippled in its current
> implementation. Is there any fundamental reason that portals can't be made
> to survive commits, like cursors WITH HOLD? This would result in a
> reasonable implementation of setFetchSize().
That would be nice to have, yes. But it would require a protocol
change which is quite a big thing to do.
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2011-10-26 06:37:03 | Re: setFetchSize |
| Previous Message | fschmidt | 2011-10-26 06:09:21 | Re: setFetchSize |