MS RFC 22a: Feature cache for long running processes and query processing (update)

[Daniel Morissette]

Steve Lime wrote:
> That could be as simple as the shape just sitting there along with the indexes, that is, the
> resultCacheMemberObj gets a new member, a shapeObj.
> 
> The result cache is nothing more than an array of those members. (e.g. layer->results) That
> could be made more high performance and hidden behind accessor methods in mapscript. Users
> use getResult(int i) already. 
> 

I like that. And you enable this query cache by default for all data 
providers that suffer from the double-pass query problem (postgis, 
oracle, etc, but *NOT* shapefiles) and provide a PROCESSING directive 
that can be used to turn off the query cache if someone wants to disable 
it to perform very large queries or for whatever reason, e.g.

   PROCESSING "QUERY_RESULT_CACHE" "OFF"

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/