RE: Does JDBC have client-side and server-side cursors like ADO/O DBC?

The official JDBC way to limit the size of that "small block of rows" is via
the setFetchSize(int) method of Statement and ResultSet. However JDBC
drivers aren't required to pay any attention to this method; some do and
some don't.

I looked in the JTOpen documentation and under AS400JDBCStatement I found
this comment under the setFetchSize() method:

<< This setting only affects statements that meet the criteria specified in
the "block criteria" property. The fetch size is only used if the "block
size" property is set to "0". >>

So that suggests to me that jt400's JDBC driver works the same way, and that
specifying those properties on the connection would probably have some
effect.

PC2

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of CWilt@xxxxxxxxxxxx
Sent: November 3, 2004 09:34
To: java400-l@xxxxxxxxxxxx
Subject: RE: Does JDBC have client-side and server-side cursors like ADO/O
DBC?

Chris,

Thanks for the info.

As far as which driver I'm using, are you looking for version info?  I'm
using the jt400 that comes with iSeries Access v5r3.

Charles Wilt
iSeries Systems Administrator / Programmer Mitsubishi Electric Automotive
America
ph: 513-573-4343
fax: 513-398-1121


> -----Original Message-----
> From: chris.delashmutt@xxxxxxxxxxxxx
> [mailto:chris.delashmutt@xxxxxxxxxxxxx]
> Sent: Wednesday, November 03, 2004 9:39 AM
> To: Java Programming on and around the iSeries / AS400
> Subject: Re: Does JDBC have client-side and server-side cursors like 
> ADO/ODBC?
> 
> 
> 
> The short answer is that it depends.
> 
> In my experience with Type 4 (remote access) JDBC Drivers, rows sent 
> lazily to the client side.  This means that only the data for a row 
> (or possibly a small block of rows) is sent to the client at once.