dojox/data/QueryReadStore (version 1.10)

This function tests whether the item passed in is indeed a valid 'attribute' like type for the store.

It throws an error if item is not valid, so you can call it in every method that needs to throw an error when item is invalid.

The request contains the data as defined in the Read-API. Additionally there is following keyword "serverQuery".

The serverQuery parameter, optional.

This parameter contains the data that will be sent to the server. If this parameter is not given the parameter "query"'s data are sent to the server. This is done for some reasons:

• to specify explicitly which data are sent to the server, they might also be a mix of what is contained in "query", "queryOptions" and the paging parameters "start" and "count" or may be even completely different things.
• don't modify the request.query data, so the interface using this store can rely on unmodified data, as the combobox dijit currently does it, it compares if the query has changed
• request.query is required by the Read-API

I.e. the following examples might be sent via GET:

fetch({query:{name:"abc"}, queryOptions:{ignoreCase:true}})

the URL will become: /url.php?name=abc

fetch({serverQuery:{q:"abc", c:true}, query:{name:"abc"}, queryOptions:{ignoreCase:true}})

the URL will become: /url.php?q=abc&c=true

// The serverQuery-parameter has overruled the query-parameter
// but the query parameter stays untouched, but is not sent to the server!
// The serverQuery contains more data than the query, so they might differ!

If the data from servers needs to be processed before it can be processed by this store, then this function should be re-implemented in subclass. This default implementation just return the data unchanged.