strk@anonymised.com wrote:
Thank you Jody, I do have a better understanding of the problem.
Now: the only function I find in postgis-0.9 is what looks
like a trigger, but it doesn't query the 'authorization_table'
as specified in the "Design Implications" document.Also, where are 'autorizationlock' and 'haveAuthorization' ?
Are them provided by GeoServer ?I think we should either move the whole logic into postgis
or into GeoServer (the latter seems better to me).
The only place to do strong transaction support is in the database (with triggers). GeoServer can call the
appropriate functions. I was talking to dblasby about this earlier today, the idea occured to me that
adding the triggers could be done in the same call as addGeometryColumn.
Adding a GeometryColumn *is* the thing that turns a regular table into a "feature" so it makes some kind of sense.
BTW: do the pdf document existing or "intentional" stuff ?
The locking "design" is provided by the Web Feature Server specification.
Those pdf documents are dated and provide a progression of our attempts to implement
WFS feature locking. The last document in the list, and the functions it indicates, were implemented
in an ealier Postgis "debug" version.
I will try and hunt down my origional email from dblasby where he provided the functions and a smaple
of calling them in the correct order.
Jody
Dave, do you have any document explaining the long-transaction needs ?
I mean: can't pgsql do it for you ?
Nope - we are looking for long term locking.
Here are the docs generated as the DataStore locking api was defined, there are even pictures!:
- http://vwfs.refractions.net/docs/Design_Implications.pdf
- http://vwfs.refractions.net/docs/DataStore_Performance.pdf
- http://vwfs.refractions.net/docs/Database_Research.pdfMost of the docs are specific to GeoServer
- http://vwfs.refractions.net/Jody