[udig-devel] Oracle plugin - what is the situation?
Chris Holmes
cholmes at openplans.org
Tue Aug 8 13:14:11 PDT 2006
>
>
> On 8/8/06, *Vitali Diatchkov* <vitali at arbonaut.com
> <mailto:vitali at arbonaut.com>> wrote:
>
>
> Hello! Some questions for persons being familiar with Oracle stuff of
> Geotools.
I guess I answer that description as well as anyone... Oracle support
has lagged a bit due to lack of a devoted module maintainer - Jody and I
do our best to help out.
>
> I am interested to investigate and possibly improve some
> functionality of
> Oracle plugin..
> We need a direct connection to Oracle database in future project
> through
> GeoTools' DataStore API with capabilities:
>
> 1) Create a direct layer in UDIG from database for rendering without any
> intermediate formats or workarounds (Oracle -> GeoServer -> WFS) - a
> kind of
> "live" layer.
Well using an Oracle plugin from GeoTools _should_ get you all the
capabilities you have Oracle -> GeoServer -> WFS, since we use the same
code base.
There can be various architecture strategies of such
> layer:
> a) Load everything from table and cache in memory (seems UDIG Oracle
> plugin
> does in a such way now if I am correct)
> b)Load only features in current viewport.
> c) some kind of mix of different strategies with caching mechanism
> and so on
I don't believe there's any in memory caching going on right now, unless
the udig oracle plugin is doing some funky stuff, which I don't believe
it is. It should work the exact same way as PostGIS, which I think is
probably closest to b). A new request is sent at every zoom - it
renders only those features which are requested, with good indexing and
the like and pretty good performance for the most part. Though not as
good as PostGIS.
>
>
> 2) Editing operations for features from this layer (in context of
> transaction) and updating database by committing.
Again, uses same api as the rest of GeoTools. I'm pretty positive we
have users doing WFS-T with oracle, so at least basic editing stuff
should work ok. Though some of it probably could use a nice rewrite,
and it's probably not super well debugged. There was a bug in this, but
I'm pretty sure I got the fix committed. If it doesn't work let me know.
>
> 3) Creating new features in layer (in context of transaction) and
> inserting
> to database by committing.
If it's an existing layer you should also be fine on this front. The
one you won't get is creating a new layer, you'll have to implement the
createSchema method for the Oracle DataStore.
>
> The UDIG can be seen as an editor for spatial data of Oracle
> database with
> basic editing functionality and advanced non-standardized solutions
> such as
> locking Area of Interest particular user for exclusive editing in
> multi-user
> environment, etc.
>
> Is anybody there who is interested in improvements of Oracle
> connection? Any
> suggestions or advises?
I'm in support, though mostly from the perspective it'll help
GeoServer's oracle support get better ;)
uDig generally has some improvements that they like for datastores. One
is definitely not doing full table scans, though I think there may have
been a fix for this somewhere. And they like the createSchema method as
well. And then they write some custom factory stuff, for the wizard and
I think to hang on to the connection. Jesse's been doing a lot of
datastore QA, so you may just check with him, and past that, you just
need to start using the oracle datastore. See where the problems are,
and ask the list on specifics. But most of the functionality should be
there, as we use it in GeoServer, your job is mostly going to be
refining it.
best regards,
Chris
>
> Vitali Diatchkov.
>
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
>
>
> !DSPAM:1003,44d8eb8c324641219810056!
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cholmes.vcf
Type: text/x-vcard
Size: 269 bytes
Desc: not available
Url : http://lists.refractions.net/pipermail/udig-devel/attachments/20060808/dc1fce1a/cholmes.vcf
More information about the udig-devel
mailing list