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.
Gilles Ganault wrote:
Hello
To write a front-end server to SQLite. To avoid locking the whole
database, I'd like to implement optimistic locking, but for this to
work, I need to use a timestamp and know which tables + records are
affected when a user sends a query that changes the database (UPDATE,
DELETE).
I guess the timestamp mechanisme can be achieved through a three-column
database: table_name, row_id, timestamp, so that, before making any
change, the server can check if any row has already been changed by
another user while the current user was still working.
Is there a way to know which rows will be changed by a query like this?
UPDATE suppliers SET name = 'HP' WHERE name = 'IBM';
Thank you
G.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
