The JDBC driver is not involved. We don't use JDBC's scrollable result
set.
On Nov 24, 2008, at 14:47, Sanne Grinovero wrote:
thanks John,
hope your back is getting better.
I've asked for more information to the reporter.
I am not expecting the JDBC driver to do the sort, it is a Lucene
so
thanks John,
hope your back is getting better.
I've asked for more information to the reporter.
I am not expecting the JDBC driver to do the sort, it is a Lucene sort, so as
you said it must be Search's code to keep something around.
Maybe we are ignoring the FORWARD_ONLY.
2008/11/24 John Griffin
I've dealt with this problem but only from an Oracle perspective. Using a
FORWARD_ONLY ScrollMode only allows the rs.next() method call. Any other
result set record movement method call results in an exception. This allows
JDBC to fetch x amount of records (set by fetch size) and then get the next
