>
> Just as a suggestion:  In most of my applications, we have a security
layer
> which is implemented through server-side functions.  These functions
keep a
> table updated which contains:
>
> lock_table
> record_id
> lock_user
> time_locked
That's an excellent and even portable idea.
>
> This allows us to avoid nasty "your update cannot be processed"-type
error
> messages by showing the user up front which records are locked, as
well as
> allowing the admin to decide when locks should "time out".
>
> I tend to find in general that database locking mechanisms are a very
poor
> locking strategy for a good UI.
>
True. But you circumvented it elegantly.

Regards, Christoph



Fri, 28 Feb 2003 10:04:55 +0100
Christoph Haller <ch@rodos.fzk.de>
Re: Can pessimistic locking be emulated?
Christoph,

> > table updated which contains:
> >
> > lock_table
> > record_id
> > lock_user
> > time_locked
>
> That's an excellent and even portable idea.

Thanks.  It's actually part of an intranet framework that my team uses to 
build all of our browser-based applications.  We've been casually discussing 
for the last few months whether to keep the framework to ourselves, or to 
take it Open Source.   Mostly we've been way too busy to make a serious 
decision ....

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

Fri, 28 Feb 2003 08:40:40 -0800
Josh Berkus <josh@agliodbs.com>
Re: Can pessimistic locking be emulated?