On Sat, Jul 10, 2010 at 04:51, panyasan <[email protected]> wrote:

>
> Hi,
>
> this one is probably for Derrell.
>
> I am using the remote table model in my application to display data that is
> well over 5.000 records (which is not much given the remote table can deal
> with much larger datasets). Wenn I scroll down the table data, hower, after
> a few request that return 50 records each, a request will be genereated by
> the model that is for 150 records, which will make the model choke and no
> more data is displayed in the table.
> Expected Result:
>
> Requests containing something like '... "params":[250,299, ...', i.e. a
> range of 50 records each.
>
> Actual Result:
>
> Four correct Requests with 50 record, then a fifth one requesting 150:
>
> ' ... "params":[850,999,8, ...'
>
> Since the first-row and last-row values are generated by the table model
> and
> passed to the implementing function _loadRowData : function( firstRow,
> lastRow ), I am assuming the bug is in the data model. Otherwise, if the
> behavior is correct, there must be a bug in my code which has to do with
> there being 150 rows instead of 50.
>

Your server code appears to be broken. It is using the second parameter not
as a "last row" value, but as a "number of rows" value. The results it
returns in the rowData member contain exactly the number of rows specified
by the second parameter, but the number of rows returned should be
(secondParameter - firstParameter).

Derrell
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to