[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: non-serializability detection
From: |
catmat |
Subject: |
Re: [Gnumed-devel] re: non-serializability detection |
Date: |
Wed, 19 Jan 2005 09:37:31 +1100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041231 |
has it been sorted out what happens after backend notifications of commits?
e.g.
backend notifies client of another user's commit
client checks if data has been dirtied by user.
if not dirtied, then
- client updates local copy of xmin, the data, and redisplays data.
if dirtied,
-client fetches changed data,
and user is showed changed data , and requested whether to :-
revert to updated data ,
revert to updated data and diff of old data and dirtied data
appended,
or overwrite updated data.
- user selects , and xmin is updated and new client dirtied data
created.