Re: [udig-users] Oracle Spatial, Editing, SRIDs and Submit Log

[Jody Garnett <jody.garnett@xxxxxxxxx>]

Hi Simon:

I created a geotools bug:
- http://jira.codehaus.org/browse/GEOT-2476

The oracle datastore is only really maintained when someone pays at
this stage (it is an unsupported module - love does not enter into it;
money or patches are what we can provided).

I went and found the code that does encoding for an update --
OracleFeatureWriter:

int srid = queryData.getFeatureTypeInfo().getSRID(type.getLocalName());
geometry.setSRID(srid);

STRUCT struct = converter.toSDO(geometry);
statement.setObject(position, struct);

There does not look to be any way to dodge the setSRID( srid ) line;
and the converter.toSDO( geometry ) method takes into account SRID.
So we have a mystery.

Jody


On Wed, Apr 29, 2009 at 5:25 PM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
>> OK, I'll help you with this. I could write a SQL script that create a test table etc. But on the uDig side, I don't know what I could do.
>
> The oracle test case for the geotools module creates its own table
> prior to executing a test; I think all we need to do is supply it some
> connection parameters and hit run.
>
> Are you signed up to the geotools-devel email list? If so we should
> move discussion there (where people can help us).
>
> The tests are here:
> - http://svn.osgeo.org/geotools/trunk/modules/unsupported/oracle-spatial/src/test/java/org/geotools/data/oracle/
>
> There are specific tests fro writing SDO objects; it could be that the
> case you supply (a polygon with a hole in it) has not been tested ...
> - http://svn.osgeo.org/geotools/trunk/modules/unsupported/oracle-spatial/src/test/java/org/geotools/data/oracle/sdo/GeometryFixture.java
>
> Nope I can see it provided as part of the test fixture...
>
> Next up we have the datastore test case:
> - http://svn.osgeo.org/geotools/trunk/modules/unsupported/oracle-spatial/src/test/java/org/geotools/data/oracle/OracleDataStoreOnlineTest.java
>
> We will add to that in order to test the problem you describe.
>
> Before we start can I ask you to try the following download out (if
> you have not already?)
> - http://udig.refractions.net/download/unstable/
>
> Their have been 4 years of geotools development (including
> improvements to the oracle datastore) since the version used in the
> uDig stable release. Perhaps the problem we are worried about has
> already been fixed.
>
> Jody
>> I tried turning on logging on the Oracle Listener but didn't get what I wanted. So I turned on session tracing and used tkprof on the server log files. I could see all the queries including the actual UPDATE statement executed against the datbase:
>
> You are smart; and tricky; individual :-)
>
> Jody
>