John Stanton <[EMAIL PROTECTED]> wrote:
You should take a closer look at the structure of Sqlite, in
particular how it uses pages. It is not amenable to your row locking strategy.

Optimistic locking doesn't lock anything per se. It's a download-modify-upload cycle where the "upload" part checks that a record being modified has not changed since being downloaded. If it has, the operation fails, and a human user is usually notified and asked to synch to the new version and try her edit again (if it still makes sense).

Optimistic locking doesn't need any special support from database engine.

Igor Tandetnik

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to