time, whichever
happens first.
[...]
Christian Bauer wrote:
[hibernate-dev] Snapshot conflict with merge
I wrote (tested and verified with Gavin):
Finally, merging doesn’t allow the following scenario, where two
modifications conflict on one snapshot:
item.getId() // The database
Hi,
The challenge is that both have merit.
The first one (dirty merge + dirty attached = exception) is more correct
from a consistency perspective.
The second one (dirty merge + dirty attached = dirty merge wins) wins is
(probably) usefull in many practical cases (and works like I think
