[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-users] udig 1.2 and oracle connection an layers
|
Comments inline...
>> What do you mean by the relational layers?
>
> I'm sorry for misunderstanding!
> Prior oracle ver.8.1 oracle stored the spatial data and index in the same
> table with the column GEOM (like potgres/postgis).
Oh I remember now; this was before they made the SDO_GEOMETRY STRUCT.
I don't think anyone ever implemented that for GeoTools (so no I don't
think that is supported).
>> It usually means that the query is taking place; it blinks as long as the
>> query is taking ...
>
> why the query is taking place?
> i mean, when i select a feature with the mouse on a active layer i'm working
> in a udig level, it's correct?
No. uDig does not load data into memory; when you click it is making a
request to the database to see what geometry you clicked on.
- when selecting - uDig just records what you have selected; but does
not load it in memory (only draws it "selected"
- when editing - it makes a request to the database and actually loads
the feature into memory; from there on you can edit the points; and
write it back to the database with the commit button
> If i import a layer from a db i make a query, when the db returns the data
> udig display the features, but it stores the data, i suppose, into a
> temporary udig data structure, right? (if not please answer, because this is
> important for me to understand the udig behavior).
Hopefully I answered that above ... uDig does not load data into
memory. We are experimenting with allowing uDig to "cache" data into
memory for uDig 1.2 - but it is an experiment and not on by default.
> So, when i click with the mouse on a feature in order to select and edit the
> shape udig perform a query? I think it's only a intersection function
> between the point's coordinates and the layer stored in udig temporary
> structure...
It is performing a query - usually a bbox query against the database.
> if udig perform a query the problem can be the database server connection or
> other like primary key... and i have to seek in this direction,
> otherwise may be a software bug... i don't know!
I wish I had an oracle handy to test and see what you are seeing.
>> If you are available when we make the next release (after to foss4g
>> conference) we would love a hand testing oracle connection support.
> you're welcome... i don't know if i'm able... i'm a newbie.
>
> really thanks for your explainations
Cheers!
Jody
