I've got a question for
JDBC specialists.
When you perform an executeQuery on a Statement like this :
Results rs = s.executeQuery("select ... where ...");
Is the ResultSet populated with ALL the rows from the query in one shot, or is it populated "on demand" when you perform a rs.next();
My understanding is that only JDBC 2.0 Scrollable Resultset offers the "on demand" feature, while with "classical" ResultSet, the whole rs is populated in one shot.
Is that correct ?
Any document on that subject is welcome.
Just to expplain my need, I want to set up a search feature in a 3-tier environment and to minimize :
- the number of access to the DB
- the amount of rows retrieve from the db when the client does not explicitally need to display them.
[ January 22, 2003: Message edited by: Bill Bailey ]