| From: | Andy Zeneski <jaz(at)ofbiz(dot)org> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Result Set Cursor Patch |
| Date: | 2004-04-30 20:51:00 |
| Message-ID: | 164902F2-9AE8-11D8-A094-000A95DA1A7C@ofbiz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Please let me know if there is anything else which would prevent this
from getting into CVS. Also, if all is good, could you please let me
know when has been committed so I can update my local tree.
-Andy
On Apr 30, 2004, at 12:58 PM, Andy Zeneski wrote:
> I expect this should take care of that issue.
>
> -Andy
>
> <pgjdbc-cursor.patch.gz>
>
> On Apr 30, 2004, at 12:29 PM, Kris Jurka wrote:
>
>>>
>>> concurrency is updatable. Is this correct? If so, I have this fixed,
>>> I
>>> am adding some test cases now and will send over a new patch.
>>
>> Right, well it's both because you can have a forward only updateable
>> resultset use a cursor because it never has to refetch, but the
>> scrollable
>> case causes problems.
>>
>> Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-04-30 23:01:53 | Re: Result Set Cursor Patch |
| Previous Message | Andy Zeneski | 2004-04-30 16:58:58 | Re: Result Set Cursor Patch |