Hi,
Suppose you have a web form to edit data from a table... you add a field
in your table which contains a version identifier for that data, then you
UPDATE ... WHERE ... AND version_id = the old version id. The version_id
is passed around in a session variable or in hidden form fields. The
Lada 'Ray' Lostak wrote:
I will also appreciate any links to web resources, talking about this
problem. I didn't find anything usefull around.
I'm working with developing a fairly big warehouse management system, and
there we see this problem every day. We've settled (many years ago) for
Hello there,
I am thinking how to solve another typical problem of online systems
with combination of thin client... Imagine simple case, 2 users are going to
edit 'same' datas. Both see on the 'screen' the same, after they started
edit them. First one changes datas and submit changes
I used to do it this way :
Suppose you have a web form to edit data from a table... you add a field
in your table which contains a version identifier for that data, then you
UPDATE ... WHERE ... AND version_id = the old version id. The version_id
is passed around in a session variable
