Cool, just a few last comments, confirming your analysis.
What I see here. Hibernate do not know a priori about how to bind hierarchy
of objects to relational model. We should configure it (through XML or
annotations) and charge the framework with such configuration. Is complex
feature type a thi
>> Sent: Friday, August 17, 2007 1:07 PM
> >> To: Vitali Diatchkov
> >> Cc: 'geotools-devel'; 'Jody Garnett'; [EMAIL PROTECTED]
> >> Subject: Re: [Geotools-devel] AbstractJDBCDataStore and its pilot
> >> implementation for Oracle Spatial
>
Vitali Diatchkov ha scritto:
> Performance benchmark is necessary thing.
> If to concern things that are new here in comparison to what I have seen in
> old OracleDataStore module:
>
> New Oracle Spatial datastore implementation is based on prepared statements
> where geometries are handled as S
PM
To: Vitali Diatchkov
Cc: 'geotools-devel'; 'Jody Garnett'; [EMAIL PROTECTED]
Subject: Re: [Geotools-devel] AbstractJDBCDataStore and its pilot
implementation for Oracle Spatial
I had a goal to implement datastore for Oracle Spatial based on GeoTools
architecture and i
l'
> Subject: Re: [Geotools-devel] AbstractJDBCDataStore and its pilot
> implementation for Oracle Spatial
>
> Do you have performance benchmark numbers vs. the old datastore? It
> sounds like really great work, but I'd like to be sure that there's a
> clear win to switching to t
> -Original Message-
> From: Rob Atkinson [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 17, 2007 1:07 PM
> To: Vitali Diatchkov
> Cc: 'geotools-devel'; 'Jody Garnett'; [EMAIL PROTECTED]
> Subject: Re: [Geotools-devel] AbstractJDBCDataStore and
I had a goal to implement datastore for Oracle Spatial based on GeoTools
architecture and interfaces to be used for direct access to Oracle database
from UDIG. GeoTools' standard implementation is very narrow and not
appropriate for high customization - I mean customization for data model
being
Morning Vitali, where would you like to go with this? I recall going
over your design and liking your work - I am afraid I contrasted it with
the ideas being put together for H2 and we got more feedback on
FeatureCollection then your implementation.
I would like to see you start up an unsupport
Do you have performance benchmark numbers vs. the old datastore? It
sounds like really great work, but I'd like to be sure that there's a
clear win to switching to the new one, since I'm sure there will be some
pain if it becomes the new default (lots of minor bugs will likely need
to be fixed
As it was mentioned earlier, reader/writer approach is not very useful in
case of features being processed through JDBC.
I had a goal to implement datastore for Oracle Spatial based on GeoTools
architecture and interfaces to be used for direct access to Oracle database
from UDIG. GeoTools' stan
10 matches
Mail list logo
