Robert wrote:
> Hi,
>
> I need to solve the "lost update problem" (when two users are editing
> the same database record, one's changes are lost when they both save
> it). I'm thinking about putting original version of the record in the
> hidden field (serialied by Storable) and upon saving do SELECT ... FOR
instead of serializing, try a message digest such as MD5 on the same data
u would have serialized. then just pass the MD5 as a hidden field and do the
comparison. i like Gerald's idea better, since many databases offer an
increment field which auto increments at each update. this would be much
faster than a MD5 since you would not have to do two selects and two
MD5 computations for each update.
--
___cliff [EMAIL PROTECTED]http://www.genwax.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
