Mikey C wrote: > Maybe I didn't make the question clear. I'm not talking about locking and > multiple writers. I'm talking about optimistic concurrency control in a > disconnected environment. > > Two processes (say a webserver). One reads some data and presents it to a > user (open - read - close). The other reads the same same data and presents > it to another user (open - read - close). The first user updates the data > (open - write - close). Several seconds/minutes later the second user > updates the same data (open - read - close). Result is the first users > changes are lost.
I usually use a timestamp for this. I believe recent versions of SQLite support auto-updating timestamps (which record the time the record was last updated). -- Nikki Locke, Trumphurst Ltd. PC & Unix consultancy & programming http://www.trumphurst.com/ ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
