Re: implementation of Statement.executeQuery()

Jon,

It has been implemented, get the latest driver.

Dave
On Mon, 2004-01-19 at 19:40, Jonathan Gold wrote:
> i know there has been large discussion in the last year or two about
> the fact that the code
>
> ResultSet rs = someStatement.executeQuery( queryString )
>
> causes an OutOfMemoryException for large result sets, as the backend
> returns the entire result set at once, and so it must be stored in
> memory while the result set exists. the current accepted solution
> seems to be the use of a result set in combination with two prepared
> statements -- one to create a cursor, the other to fetch from it.
> there was some comment in these threads that it would be nice if that
> could be fixed, and to have this functionality added to the jdbc
> implementation for postgres.
>
> what is the state of this? do people still want to do it? if so, is
> anyone working on it yet?
>
> jon
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
Dave Cramer
519 939 0336
ICQ # 1467551