Gabriel,
The cost involved in finding the bounds can be very high.
For example, consider a 1GB shapefile where you're doing the query
"WHERE name='dave blasby'". This would require reading the entire DBF
file twice. Once to determine the bounds of the result, and once to
actually calculate the result. For this query, spatial indexing isnt
going to help since the query isnt spatial.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
right.
I still think that should be up to the DBA responsibility (and to have
indexing capabilities for shapefiles and ohter file based datastores).
Anyway, what you're proposing is to have a switch in geoserver so one
can enable/disable the getBounds() call. No complaints about that.
cheers,
Gabriel.
On Tue, 2005-06-07 at 11:54 -0400, dblasby@anonymised.com wrote:
Gabriel,
The cost involved in finding the bounds can be very high.
For example, consider a 1GB shapefile where you're doing the query
"WHERE name='dave blasby'". This would require reading the entire DBF
file twice. Once to determine the bounds of the result, and once to
actually calculate the result. For this query, spatial indexing isnt
going to help since the query isnt spatial.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/