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