Re: how to auto GRANT custom ACL on a new table?

[Maciej Sieczka <tutey(at)o2(dot)pl>]

Richard Huxton pisze:
> Maciej Sieczka wrote:

> > In PG experts 
> > opinion, could/should a PostGIS editing software lock table for 
> > writing to prevent concurent editing?

> The application should either:
> 1. Take an advisory lock (see the functions/admin functions chapter) so 
> that it can use another table to indicate which parts of the GIS are in 
> use.
> 2. Check to see if the data changed while the user was editing but 
> before committing (known as "optimistic locking"). Then give the user 
> the option to overwrite/rollback.
>
> A last resort would be locking rows or the whole table, since a user 
> might click "edit" then go to lunch.
>
> Certainly doing nothing isn't much use if you have multiple users editing.

Thanks Richard!

I've forwarded your remarks to QGIS devs [1].

Maciek


[1]http://www.nabble.com/forum/ViewPost.jtp?post=15699694&framed=y