we have found a statement executed by Geoserver using the Oracle-Spartial
Plugin that has got
a very high cputime-usage.
SELECT SDO_TUNE.EXTENT_OF('MYTABLENAME, 'GEOLOC') from dual
I think this Statement will be called if the getEnvelope() an
getBounds(Query) Methods of the Oracledatastore will be used and and no
Filter ist set.
We see that this Statement will be executed only once a day.
We think that this Statement calculates the Extend of the Featuretype.
E.g. shown in the Capabilitiesdocument.
Is it possible to switch this calculation off and only use the given extends
defined in the info.xml file of the FeatureType?
we have found a statement executed by Geoserver using the Oracle-Spartial
Plugin that has got a very high cputime-usage.
SELECT SDO_TUNE.EXTENT_OF('MYTABLENAME, 'GEOLOC') from dual
I think this Statement will be called if the getEnvelope() an
getBounds(Query) Methods of the Oracledatastore will be used and and no
Filter ist set.
We see that this Statement will be executed only once a day.
We think that this Statement calculates the Extend of the Featuretype.
E.g. shown in the Capabilitiesdocument.
Is it possible to switch this calculation off and only use the given extends
defined in the info.xml file of the FeatureType?
The other way to shut it off is to fill the the metadata for your table; I am not sure if the oracle datastore checks every possible case (probably only the ones I was using at the time) - but if it can understand the metadata it will not need resort to trickery like the above.
we have found a statement executed by Geoserver using the Oracle-Spartial
Plugin that has got a very high cputime-usage.
SELECT SDO_TUNE.EXTENT_OF('MYTABLENAME, 'GEOLOC') from dual
I think this Statement will be called if the getEnvelope() an
getBounds(Query) Methods of the Oracledatastore will be used and and no
Filter ist set.
We see that this Statement will be executed only once a day.
We think that this Statement calculates the Extend of the Featuretype.
E.g. shown in the Capabilitiesdocument.
Is it possible to switch this calculation off and only use the given extends
defined in the info.xml file of the FeatureType?
The calculation should happen only if GeoServer does not have a native bbox available (I believe). To have the native bbox around you need to
use "generate bbox" button and then save, or fill it manually in the
info.xml file and then force geoserver to reload. If that command is
still issued after that, we have a bug somewhere (and we'll need some
way to determine what request is triggering that bbox computation).