Re: Queries with large ResultSets

Поиск
Список
Период
Сортировка
Искать
От
Andrea Aime
Тема
Re: Queries with large ResultSets
Дата
в 17:56:38
Msg-id
200405202256.41349.andrea.aime@aliceposta.it
Ответ на
Список
Дерево обсуждения
Queries with large ResultSets Jack Orenstein <jao@geophile.com>
Re: Queries with large ResultSets Oliver Jowett <oliver@opencloud.com>
Re: Queries with large ResultSets Kris Jurka <books@ejurka.com>
Re: Queries with large ResultSets Andrea Aime <andrea.aime@aliceposta.it>
Re: Queries with large ResultSets Tom Lane <tgl@sss.pgh.pa.us>
Re: Queries with large ResultSets Andrea Aime <andrea.aime@aliceposta.it>
Re: Queries with large ResultSets Dave Cramer <pg@fastcrypt.com>
Re: Queries with large ResultSets Andrea Aime <andrea.aime@aliceposta.it>
Re: Queries with large ResultSets Oliver Jowett <oliver@opencloud.com>
Re: Queries with large ResultSets Dave Cramer <pg@fastcrypt.com>
Re: Queries with large ResultSets Tom Lane <tgl@sss.pgh.pa.us>
Re: Queries with large ResultSets Oliver Jowett <oliver@opencloud.com>
Re: Queries with large ResultSets Andrea Aime <andrea.aime@aliceposta.it>
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
В списке pgsql-jdbc по дате отправления
От: Dave Cramer
Дата:
От: Oliver Jowett
Дата:
FAQ