AW: Best practice for entity update.

2007-02-12 Thread Thomas Fischer
We have implemented something similar. What you are asking for is called optimistic locking and it is usually done using triggers. See e.g. http://orafaq.com/papers/locking.pdf Our implementation is on oracle 9i: It increases a check column on each update by one. The following sql creates the

AW: Best practice for entity update.

2007-02-09 Thread Thoralf Rickert
Hi! If it isn't possible to use a transaction connection you can use a timestamp column to verify if the row is changed in the database. Before saving the instance you can read the timestamp column from the DB and compare it with the timestamp that is set in your instance (this should be done