is there a method to record somewhere in geoserver the result of the following query executend on a Oracle DB ?
SELECT SDO_AGGR_MBR(SHAPE) as boundingbox from DBMCOLTUREAGRICOLE
What do you mean record? Cache?
The request is normally run only when you configure the layer and ask for teh native bbox to be computed,
and can take a lot of time indeed.
If you have a view indeed there is no faster way, but you can specify the bounds manually
if you know them
2013/2/20 Andrea Aime <andrea.aime@anonymised.com>:
On Wed, Feb 20, 2013 at 5:10 PM, mbagazzi@anonymised.com
<maurobagazzilavoro@anonymised.com> wrote:
Hello everybody,
is there a method to record somewhere in geoserver the result of the
following query executend on a Oracle DB ?
SELECT SDO_AGGR_MBR(SHAPE) as boundingbox from DBMCOLTUREAGRICOLE
What do you mean record? Cache?
The request is normally run only when you configure the layer and ask for
teh native bbox to be computed,
and can take a lot of time indeed.
If you have a view indeed there is no faster way, but you can specify the
bounds manually
if you know them
I thougth that values were extracted from all_sdo_geom_metadata , but
there should be a good reason not to do that.
Would it be a problem having an extent not equal to real extent of all
features in the featuretype?
As usual thanks a lot for you patience and expertise
I supposed that this request was executed just during the configuration of the layer.
Anyway, analyzing my DB today I found this query among the others and I wonder because I am sure none had modified the configuration recalculating the mbr.
Sometimes, it happens also for others layers that, I am sure, none can modify/recalculate.
How is it possibile for you?
is there a method to record somewhere in geoserver the result of the following query executend on a Oracle DB ?
SELECT SDO_AGGR_MBR(SHAPE) as boundingbox from DBMCOLTUREAGRICOLE
What do you mean record? Cache?
The request is normally run only when you configure the layer and ask for teh native bbox to be computed,
and can take a lot of time indeed.
If you have a view indeed there is no faster way, but you can specify the bounds manually
if you know them
is there a method to record somewhere in geoserver the result of the following query executend on a Oracle DB ?
SELECT SDO_AGGR_MBR(SHAPE) as boundingbox from DBMCOLTUREAGRICOLE
What do you mean record? Cache?
The request is normally run only when you configure the layer and ask for teh native bbox to be computed,
and can take a lot of time indeed.
If you have a view indeed there is no faster way, but you can specify the bounds manually
if you know them
is there a method to record somewhere in geoserver the result of the following query executend on a Oracle DB ?
SELECT SDO_AGGR_MBR(SHAPE) as boundingbox from DBMCOLTUREAGRICOLE
What do you mean record? Cache?
The request is normally run only when you configure the layer and ask for teh native bbox to be computed,
and can take a lot of time indeed.
If you have a view indeed there is no faster way, but you can specify the bounds manually
if you know them
Trying to give a cumulative answer on the various mails piling up on this thread:
The metadata tables are not inspected because admins don’t normally fill them with useful
information. If someone want to provide a patch that allows to look into them when a certain
configuration flag is enabled, that would be welcomed
The current code tries to use SDO_TUNE.EXTENT_OF before falling back on
envelope aggregation with SDO_AGG_MBR, that works only for tables (not for views afaik),
and there was a recent fix on the usage of SDO_TUNE.EXTENT_OF when trying to access
a table that is not in the user own schema
If you have suggestions on how to improve things let’s discuss them and then open
a improvement request on jira.codehaus.org, waiting for someone to sponsor its development
or some developer that wants to spend some of his spare time on the Oracle connector