× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Larry,  

In terms of SQL paging, the AS400 JDBC driver won't read the entire results.
It can be controlled by the "block size (specified on JDBC connection
props)" and the number of times you iterate over your resultSet.next().  So
what we do is read a set of records based on how many records the user wants
at a time, return that set and then allow them to request more.  Once they
want more we then return the 2nd set of records and so on.  Tricks are to
control if you should hold the connection between requests, block size, and
retain memory of where each user is in terms of the paging  (user x is on
records 300-350 of query x).  

Here is an example:
http://www.planetjavainc.com/wow63x/runApp?id=369&_pj_lib=wowsamp60  

Under "JDBC Statement Controls" you can set the sql statement, row count,
and label.  Change the values then click "update sql" and then run that sql
using "JDBC Statement".  

This is part of a free utility we offer if you need this function.  

HTH  

Paul Holm

www.gotwebdata.net  
iSeries Web Apps in 30 seconds
pholm@xxxxxxxxxxxxxxxxx    


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.