Paladin does not use the concurrency check, so the last save is updating the table.
This was confirmed in a very old post from 2004 .
I am comparing the way Paladin works with one previous prototype based in datasets.
Using datasets you only need to update it. As the dataset load internally the original value an the new, previous to the update of the row the original value of the dataset was compared with the one in the table, and an concurrency advise is arised, already included in the returned dataset. This is very simple and easy to use.
Of course it can not be so easy to implemented it into Paladin.
What do you plan about it?
At the moment, there are no plans to add anymore new features into the 0.9.0 release. Development of the framework will be frozen and an RTM version of 0.9.0 will be released soon.
I do not plan to develop it further on .NET 1.1. I would like to pick-up .NET 2.0 and hopefully, have the time (and permission) to develop Paladin-II. Currently, I'm going through the finalizations to decide whether the source should be made available to the public.
I will keep everyone informed.