The problem we have is that to efficiently process result sets from database-based drivers we need to reference rows in the result set rather than rows in the dataset. That means the results (with those types of DATA/CONNECTIONs) can't be cached using the current mechanism. Shapefiles would still work ok.
The faster query processing is much faster, as much as 24x faster with DB-based data that it's not practical to do things the old way. Steve >>> Martin Kofahl <[email protected]> 03/15/09 2:35 PM >>> We use them with MapScript. Maybe it's possibile to activate saved queries only with with a compiler option? Steve Lime wrote: > Hi all: Consider this a survey of sorts. I'm wondering how many of > you make use of saving queries, either via the CGI or MapScript. It's > an old feature that isn't terribly useful and I'm trying to > understand the pain the community might incur if they go away in 6.0. > If you didn't know they existed or how you might use them then it's > safe to say you don't need 'em. > > Steve _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
