Thanks for the
hint. I'm using Glorp and this introduces this
particular error. Getting an object from the database gives
the object whichyou can edit. But the instances variables
are only Proxies. And this disturbed Magritte. I don't know
exactly why but a wild guess would be the difference between classes:
and the class of the Proxy.
thanks again,
Norbert
You could probably fix it by implementing
= anObject
^self == anObject yourself
Forcing the proxy to resolve. This is basically what I had to do
in the
MagritteGlorp ActiveRecord package to avoid the same error.
Or change the way objects are cached, see the subclasses MAMemento.
We once used OmniBase together with Magritte and there we introduced
a special subclass of MAMemento resolving proxies and validating
changes with respect to the database (conflicts, concurrent
modifications, etc). I guess something like that could help in your
context as well.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch