Probably a question better answered by OGR maintainers... In theory working off a single result set, even if you have to traverse it more than once, would be far more efficient than id-based lookups done now.
Steve -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brent Fraser Sent: Tuesday, December 22, 2009 2:55 PM To: Lime, Steve D (DNR) Cc: [email protected] Subject: RE: [mapserver-users] mapserver 5.6.0, RFC 52 and driver support Do you think there would be any point in making the changes for OGR (for my ODBC -> Sql Server connection)? If so, I'll start having a look at the code... Brent > The improvements are limited to native drivers only, principally Oracle > Spatial and PostGIS. > > Steve > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Brent Fraser > Sent: Tuesday, December 22, 2009 2:48 PM > To: [email protected] > Subject: [mapserver-users] mapserver 5.6.0, RFC 52 and driver support > > To all, > > I've got a query performance problem I'm trying to track down. I was > hopeful that 5.6 with RFC 52 implemented might help me, but it seems to > have no impact. > > Are the changes for RFC 52 implemented for OGR ODBC connections? > > Thanks! > Brent Fraser > > _______________________________________________ > 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 _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
