Peter Mount <peter@retep.org.uk> writes:
>
> For JDBC2, I'm planning (may get done for 7.1) an alternate ResultSet
> class that uses cursors. This would speed things up as the entire
> resultset isn't received in one go. That's the biggest bottleneck of them
> all.
>
I would think this depends on the queries you execute. Is it any overhead on
the backend side related to retrieving results through the use of
cursors(ignoring the extra bytes sent) ?
If you only use a fragment of the data in the result set this method would
of course be faster, but in other situations I'm concerned that you will
only add overhead to the ResulSet.next() method(with familiy). But you
mentioned alternate implementation, so that would probably mean that the
user can choose the appropriate implementation for his application ?
Regards,
Gunnar
