On 16/09/2010 12:17, Strangmann, Moritz wrote:
> Hi,
>
> At first I want to excuse for my English. But I will try my very best.
>
> I actually assumed that the Oracle extension for GeoServer only uses
> locator features of the Oracle DB. Well, my DB Admin has said that this
> is not the case.
> So I have to find out what parts of my App are using spatial features.
>
> On a first view at the source code I noticed that the class
> OracleFilterToSQL uses the function SDO_RELATE. This is according to the
> following page only for Spatial allowed:
> http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_locat
> or.htm#i632018

The document there speaks about SDO_GEOM.RELATE, not directly about
SOD_RELATE. That said, I have no idea if internally SDO_RELATE calls to
SDO_GEOM.RELATE or not.


> Is there a simple way to eliminate or disable all the spatial features?

The Oracle specific calls are located in OracleFilterToSQL and
OracleDialect.
Not being able to use SDO_RELATE will cripple proper WFS spatial filter
support.
When the native database does not support certain filters we change
the filter capabilities so that they don't declare support for those
filters and end up just doing the filtering all in memory, which can 
have significant overhead.
The code should either receive a flag that it's not playing against
a spatial enabled db or have some way to figure out the limits of the
database on initialization and setup the filter capabilities accordingly.
For better performance it would be nice to at least send a BBOX filter
down the the db and then perform the secondary filter in memory,
but I'm not sure if the current unified jdbc store code has an option
to do that. It's probably the only sane option if you actually need
non trivial spatial filters and have significant amount of data
though.

Ah, one thing, if you're just using WMS I'd suggest you enable the
"loose bbox" flag in the store configuration and be done with it,
it will make the store just use the primary filter for all bbox
requests: SDO_RELATE is necessary only if you need the other spatial
filters, like overlap, disjoint, and so on

Cheers
Andrea

-- 
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to