21 Aug
2008
21 Aug
'08
10:24 p.m.
User: Input is conflicting with concurrent
modification
In my case, my object being edited through Magritte was read in by
Glorp..
I'm using Keith's RealMemento (on VW).. I believe it thinks that the
objects
are different even though I made no changes. I guess its safe to
assume I need
to see why the comparison is failing? Any other suggestions would
be appreciated!
Magritte probably things that there is a conflict because GLORP
doesn't keep the identity of objects and you don't properly implement
#= in all the involved objects.
If the DB handles commit conflicts for you, there is no need for
Magritte to do these checks for you. I remember doing some special
memento class for OmniBase that used the mechanisms of the OODB to
check for conflicts and to mark the changed parts as dirty.
If you don't want to check for conflicts you can simply replace the
method Object>>#mementoClass to return MACachedMemento.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch