| From: | Scott Lamb <slamb(at)slamb(dot)org> | 
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org | 
| Subject: | Re: streaming result sets: progress | 
| Date: | 2002-11-15 13:00:26 | 
| Message-ID: | 3DD4EFEA.1030307@slamb.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-jdbc | 
First, my understanding is that cursors are only valid within the 
transaction in which they were created. Is this correct?
If so, I can't use the cursor method exclusively. Some of my code needs 
to be able to iterate over a resultset and execute whole transactions 
based on it. With cursors, it would fail after the first iteration of 
the loop.
 From the archives, Barry Lind's plan at one point was to not use 
cursors unless setFetchSize() was used explicitly. [*] That would keep 
existing code working. Or otherwise, they should not be used if I 
specify ResultSet.HOLD_CURSORS_OVER_COMMIT; I could add that to my code 
where it is important. If/when the backend changes to support holding 
cursors over commit, then they could be used in all cases.
Does this sound reasonable?
Thanks,
Scott
[*] - <http://archives.postgresql.org/pgsql-jdbc/2002-07/msg00164.php>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | nferrier | 2002-11-15 13:22:32 | Re: streaming result sets: progress | 
| Previous Message | nferrier | 2002-11-15 10:30:33 | Re: streaming result sets: progress |