[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mapbender-users
Subject:    Re: [Mapbender-users] [Fwd: WFS transactions]
From:       Balázs Bámer <bamerbalazs () gmail ! com>
Date:       2009-03-26 21:13:44
Message-ID: f76b69190903261413q3d750e21qab8be9ce581b994 () mail ! gmail ! com
[Download RAW message or body]

Hi Christoph,

> d.del(0)
> you would have to call
> dbGeom("delete", 0)

This definitely would solve the problem, but as I saw in function
class_wfs.transaction, each WFS request is wrapped in its own
transaction: class_wfs.wrapTransaction gets exactly one, it is also
mentioned in a remark:
// I assume that only one feature is contained in the GeoJSON,
                // so I just take the first from the collection.
which method of operation doesn't make use of the WFS transactions and
possibly could lead to corrupted WFS store. I try to start on a
solution which would

What do nonTransactionalEditable and isTransactional mean? Or by the
time the task is to perform WFS changes, they don't have any meaning?

Thank you.
Best regards: Balázs Bámer
_______________________________________________
Mapbender_users mailing list
Mapbender_users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapbender_users

[prev in list] [next in list] [prev in thread] [next in thread]