> Just setting a binary lock value in the table will lock it for
> everybody, including the person who owns the lock and is allowed to edit
> it.
>
> My cms uses an application-scoped 2d array that holds the record's
> primary key, the user ID of the person 'owning' the lock and a timestamp
> value.
This might be overkill for this application, but nevertheless an
entertaining read on concurrency control:
Concurrency Control and Recovery in Database Systems
ftp://ftp.research.microsoft.com/users/ccontrol/ccontrol.zip
Jochem
--
I don't get it
immigrants don't work
and steal our jobs
- Loesje
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
