That was an oversight. I'll change the implementation to take an expression and fix the 0-based indexing.
When you find any bugs, I'd encourage you to file them using the Apache Software Foundation Bug database. It makes it easier to address and track the bugs. Here's the URL: http://nagoya.apache.org Program: Taglibs Component: Standard Taglib (for JSTL reference implementation related bugs) Thanks! Justy ----- Original Message ----- From: "Wolfgang R�ckelein" <[EMAIL PROTECTED]> To: "Tag Libraries Users List" <[EMAIL PROTECTED]> Sent: Sunday, February 03, 2002 2:28 PM Subject: Re: Problem with sql query startRow attribute Hi, Wolfgang R�ckelein wrote: > the documentation suggests to use the startRow attribute of the query as > a "poor man's" way to page through a bigger result set: Increase > startRow on each page by maxRow. > > However, for this to work, the startRow attribute should take an > expression, instead of requiring a int directly as it is currently the > case (I checked it in the nightly source code, the setter method is in > the common class instead of the rt and el classes). Additionally, StartRow seems to be 1-based, i.e. StartRow="0" and StartRow="1" produce the same result, StartRow="2" skips the first row. This is a bit inconstistent that row indexing is now 0-based. Greetings, Wolfgang -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
