Hi Torsten:
I am also using:
<esql:use-limit-clause/>
<esql:skip-rows>1</esql:skip-rows>
<esql:max-rows>4</esql:max-rows>
You have no way to trigger the <esql:more-result> tag.
Currently in my test DB on PostgreSQL there are more that 8,000 rows and
this does not trigger the <esql:more-results> tag. As you can see I setted
the <esql:maxrows> to 4.
This is why I started thinking about this issue and suggested the
workaround. I think the solutions is not too ugly because is better to get
5 rows in a resultset than 8,000 or more, just to get the row number 5 and
trigger the <esql:more-results> tag.
Regards,
Antonio Gallardo.
Torsten Curdt dijo:
> I must have missed you previous posts... :-/
>
> <snip/>
>
>> to:
>> if (getMaxRows() > -1) sb.append(" LIMIT ").append(getMaxRows()+1);
>>
>> that way, when we will request maxrows=4 the code will limit the query
>> to 5 (4+1) and there will be another row that will trigger the
>> <esql:more-results> tag.
>
> Hm... this sounds like an very ugly work around. We better check the
> loop and the more-results condition.
>
> <snip/>
>
>> > I was checking the code behind esql. I think the problem is related
>> to the new LIMT OFFSET in the Query:
>> >
>> > If we set the limit of returned rows the database will return in the
>> recordset only the numbers of rows that we requested with the LIMIT
>> keyword. That means that we cannot know if there are more rows. XSP
>> does not know it too and then the <esql:more-results> do nothing.
>
> This shouldn't be a problem since we (already) can get the total number
> of rows with a count query. (see the query classes)
>
> I'll have a look...
> --
> Torsten
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
