db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen" <Bernt.John...@Sun.COM>
Subject Re: Streaming Results
Date Thu, 14 Jan 2010 09:08:01 GMT

Some general remarks (don't remember the exact details of what Derby
actually does with setFetchSize).

>>>>>>>>>>>> Stian Brattland wrote (2010-01-14 08:43:32):
> Hi,
> I've got a question regarding results streaming. The J/Connector for  
> MySQL supports results streaming, which means
> that you can stream and process rows in a ResultSet one by one.  
> Normally, all rows in a ResultSet will be retrived
> before you can process the ResultSet. However, i am curious as to wether  
> this "feature" also exists in Derby?

Normally, a JDBC driver will retrieve a suitable number of rows, not
necessarily all, depending on various factors such as row size, number
of rows resulting from the query and communication buffer size.

> In MySQL, you would do the following to stream results from the database  
> as you iterate through a ResultSet:
> stmt = conn.createStatement(java.sql.ResultSet.TYPE_FORWARD_ONLY, java.sql.ResultSet.CONCUR_READ_ONLY);
> stmt.setFetchSize(Integer.MIN_VALUE);

setFetchSize is just a hint to the driver, See


A well written driver will still try to do thing's optimal, such as
e.g. fill up the communication buffer with rows to reduce the number
of roundtrips, regardless of how low you set the fetchSize.

And last, why would you like to force the driver to fetch the rows one
by one? The only thing you will get fromthat, is extra overhead.
Bernt Marius Johnsen, Staff Engineer
Database Technology Group, Sun Microsystems, Trondheim, Norway

View raw message