Re: [Geoserver-users] Using the new oracleNG plugin

[Kris G. <kge...@xe...>]

Hi Andrea,

I see the new one is setting the srid parameter to NULL also only
internally handling it as -1 I guess
The old pluggin worked without the filling of the user_sdo_geom_metadata
table yes.
Don't exactly know why though (might try the verbose logging on the old
one later to find out some more)
I think setting the user_sdo_geom_metadata of the other user (the one
used for the connection and with the synonym) seems like a good thing.

Cheers  Kris

-----Original Message-----
From: Andrea Aime [mailto:aa...@op...] 
Sent: Tuesday, March 10, 2009 2:50 PM
To: Kris Geusebroek
Cc: geo...@li...
Subject: Re: [Geoserver-users] Using the new oracleNG plugin

Kris Geusebroek ha scritto:
> I made some progress myself.
> 
> I can see in the sourcecode of the oracle plugin that a query is done
to 
> the table USER_SDO_GEOM_)METADAT to get the SRID for the table
> 
> In my config this table is empty because we use a table from another 
> user by public synonym.
> 
>  
> 
> So I think I need to update the USER SDO GEOM METADATA table for this 
> user too.
> 
> Any other options are appreciated

There is none that I know of, Oracle pretends that the srs of the
bbox and whatever else used in a spatial index is equal to the
one of the indexed geometries.
You say that the old oracle spatial datastore was working properly
for you? I'm wondering how, the old datastore was getting the
srid in pretty much the same way and was encoding the srid as well.

Humm... I see the old was encoding NULL as the srid when it was not
known, whilst I guess the new one is encoding -1. That is probably
the relevant difference? Can you try running manually a query
that uses NULL and see if Oracle complains about it?

Cheers
Andrea

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