From: Dylan Tynan
Sent: Saturday, November 29, 2008 12:38 PM
To: 'dojo-interest <at> dojotoolkit.org'
Subject: RE: [Dojo-interest] Grid & JsonQueryRestStore - setQuery & filter

Here's an example page of what I'm doing & seeing:  http://tpsreports.realsage.biz/qtest2.html

Here's the same thing and I added a little bit of console logging into a couple of the files:  http://tpsreports.realsage.biz/qtest3.html

(dojo code is current as of today)

 

You'll see the grid initially has about 500 rows.  Hit the button to filter and it selects those with myid > 90, which seems to work, but I only get the first 50 rows of that resultset with no way to scroll to the rest.  Hopefully I'm just doing something stupid (or not doing something smart)

 

I've tried everything I can think of .... ideas?

 

Thanks a bunch,

Dylan Tynan

From: dojo-interest-bounces <at> dojotoolkit.org [mailto:dojo-interest-bounces <at> dojotoolkit.org] On Behalf Of Dylan Tynan
Sent: Friday, November 28, 2008 2:10 PM
To: dojo-interest <at> dojotoolkit.org
Subject: [Dojo-interest] Grid & JsonQueryRestStore - setQuery & filter

I just found JsonQueryRestStore in the nightlies.  This appears to be the store that Krys mentioned that would give you client-side querying and paging, without using PersevereStore.   (this email supersedes my prior email about jsonreststore & number-of-rows-in-results & grid).

 

I've been playing with it with ClientFilter loaded first and cache=true and it does seem to give me client-side jsonQuery capabilities.  I attached my store to a DataGrid and loaded all my data from a URL. This works well, I can scroll down the grid & see all the rows, each rendering rowsPerPage number of rows at a time.  I can then do a setQuery on the grid and I can use jsonquery syntax & I get the right results updating into the grid from the in-memory copy of my data (ie no new server requests).  Awesome!  That's what I want.  However, I'm only getting 50 rows back (double the rowsPerPage value) into the grid once I issue the setQuery. (basically double the number of rows of whatever rowsPerPage is, which looks like how the code reads).  I have about 1000 rows of data, and about 400 or so match my query, so once I setQuery (or filter()) then I'm missing 350 rows in the grid & they won't appear when I scroll up or down.  Should this work?  Do I need to override a method somewhere or something, or is there an alternate call I should be using?

 

Thanks,

Dylan Tynan