> Just as a suggestion: In most of my applications, we have a security
> which is implemented through server-side functions. These functions
> table updated which contains:
That's an excellent and even portable idea.
> This allows us to avoid nasty "your update cannot be processed"-type
> messages by showing the user up front which records are locked, as
> allowing the admin to decide when locks should "time out".
> I tend to find in general that database locking mechanisms are a very
> locking strategy for a good UI.
True. But you circumvented it elegantly.
pgsql-hackers by date
|Next:||From: Andreas Schmitz||Date: 2003-02-28 09:16:29|
|Subject: Re: Still a bug in the VACUUM ??? !!!|
|Previous:||From: Christopher Kings-Lynne||Date: 2003-02-28 07:50:21|
|Subject: Are my emails getting through at all???|