| From: | Andrea Aime <andrea(dot)aime(at)aliceposta(dot)it> |
|---|---|
| To: | pg(at)fastcrypt(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, Jack Orenstein <jao(at)geophile(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Queries with large ResultSets |
| Date: | 2004-05-20 20:56:41 |
| Message-ID: | 200405202256.41349.andrea.aime@aliceposta.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Alle 22:03, giovedì 20 maggio 2004, Dave Cramer ha scritto:
> You can use a holdable cursor, and get a cursor outside of a
> transaction, but beware, postgres has to store this somewhere, and it's
> not update-able
Store it somewhere means that it has to write the result of the query
to persistent storage and then provide scrolling over it? It's not the
best way to do things since in the case of geoserver the query result
can be several megabytes (gis data)...
Anyway, how do I get such a cursor using the JDBC driver?
Moreover, would the hack of calling commit() at the end of every operation
in order to simulate an autocommit connection work?
Best regards
Andrea Aime
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dam Avalos | 2004-05-20 22:54:20 | a big question |
| Previous Message | Dave Cramer | 2004-05-20 20:03:33 | Re: Queries with large ResultSets |