We have strong transaction support functions added to Postgis - just for use by geotools2 datastore.
By subclassing PostgisFeatureStore and supporting the FeatureLocking api using the database functions we will finally have real locks!
This is a requirements for vwfs M4 deadline
CodeHaus Comment From: jgarnett - Time: Thu, 5 Feb 2004 16:21:59 -0600
I need to be able to trust the FeatureWrtier before I can proceed.
Please note that having the FeatureWriter broken on remove - is really bad. The use of an optimized FeatureSource has hidden this bug from GeoServer - but we cannot pretend that the PostgisDataStore is working
at the moment.
If a user tries to use the low-level api (or even the non optimized FeatureSource) they will run into our inconsistent FeatureWriter.
CodeHaus Comment From: jgarnett - Time: Wed, 5 Mar 2008 15:47:56 -0600
I am no longer sure if the locking functions are included in PostGIS, lets assume this effort is abandoned due to lack of interest / money.