Re: AW: [dbforms] Classic navigation reads too many rows

[pvseznam]

I just looked at profiler how classic navigation works but there was only a select statement and it looked like too many data are read. MaxRows parameter was missing in profiler report. It is clear now. What's concern of the normal navigation, I think that it would be still useful to keep an option of limiting number of rows in mind. Thanks Henner for your explanation, Pavel This is used in classic navigation! Henner -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of pvseznam Sent: Tuesday, January 24, 2006 1:27 PM To: jdbforms-interest@lists.sourceforge.net Subject: Re: AW: [dbforms] Classic navigation reads too many rows I still would like to be able to limit number of rows transfered from a database. TOP statements are database specific but probably it might be possible to use a method of Statement - setMaxRows(), something like: "Statement stmt = conn.createStatement(); stmt.setMaxRows(myLimit); ...". I think it could be useful for both kinds of navigation. As a parameter for a new one and internally in the classic one. Pavel Classsic navigation uses an algorithm which nobody understands any more. Inclusive the developer.. It's not generation TOP statements, because they are database specific. Instead of this it tries some key manipulation in the query. Most of the newer features do not work with classic navigation. It's really unmaintenanced - becauss nobody knows how it works. The newer navigation also retrieves the rows which you want to see - so it's no problem if you can not filter effectively. It will fetch the rows side by side if you use maxRows=40 You could get a memory problem if you view a large recordset. Then you must increase the mem size for you servlet machine. Regards Henner Hi, I am trying to use a classic navigation because my tables are growing and I can't filter queries effectively. I expected, that if I specify maxRows=40, only 40 records would be read. Yes, I don't know how the select command should look like generally for any database. But for MS SQL it is "select top 40 * from myTable". Let say myTable is ordered by myTableId which is 1, 2, 3, 4.... It seems that in the classic navigation after next button following selects are used: select * from myTable where myTableId > 40 select * from myTable where myTableId > 80 select * from myTable where myTableId > 120 and I would like to get select top 40 * from myTable where myTableId > 40 instead. I think it is a problem for everyone who works with classic navigation and therefore there might be a known way to solve my problem? Maybe via an interceptor? Thank in advance Best Regards Pavel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ DbForms Mailing List http://www.wap-force.net/dbforms