On Monday 16 August 2010 12:56:33 pm Ivano Malavolta wrote:
> Hi Mauricio,
> thanks for the info.
> However I still do not manage to save layers coming from a Postgis DB.
> Here is my workflow:
> 1) open a layer from the PostGis: ok, the layer correctly appears in
> the Layers View
> 2) modify some
Thank you Jody, of course it worked like a charm :)
Best regards,
Ivano
>uDig has a commit / rollback workflow. So you can edit, perform operations and
>so on, and when you are happy with the result press the commit button. For
>databases any >information you modified is handled by a database
Hi Mauricio,
thanks for the info.
However I still do not manage to save layers coming from a Postgis DB.
Here is my workflow:
1) open a layer from the PostGis: ok, the layer correctly appears in
the Layers View
2) modify some geometry within the layer: ok
3) finish the editing of the layer selectin
uDig has a commit / rollback workflow. So you can edit, perform operations and
so on, and when you are happy with the result press the commit button. For
databases any information you modified is handled by a database transaction;
for a shapefile any changes are held in memory (only the changes
On Monday 16 August 2010 10:48:04 am Ivano Malavolta wrote:
> Hi all,
> I need to know if uDig really works in real-time on Oracle and Postgis DBs.
> In other words, can I modify a layer directly on an Oracle DB?
> I mean, can I load a layer from an Oracle DB and store the modifed
> geographic data
Hi all,
I need to know if uDig really works in real-time on Oracle and Postgis DBs.
In other words, can I modify a layer directly on an Oracle DB?
I mean, can I load a layer from an Oracle DB and store the modifed
geographic data
on the DB again?
For example, in Qgis when I modify a layer and I st
