Hello Chris,
the point is: I am changing the lexical term object (the object used as an index) independently (without knowing about) of the objectS (from the Magma collection) this term is an attribute of (and used as an index). These lexical terms design a classification, existing independently
Do you mean I just need to send #noteOldKeys: with the lexical term as an argument? I thought this message should be used with the object from the Magma collection using the lexical terms as an index.
Hilaire
Le lundi 18 mai 2009 à 09:49 -0500, Chris Muller a écrit :
Hi Hilaire, yes #noteOldKeys: (or whatever it is) needs to be sent if the hash value changes.
But this should not require an enumeration! If you have the object which you are changing, and you have access to the session, you should have everything you need, no need to iterate..
Just be sure to noteOldKeysFor: *before* you make the change, that way the correct old key is noted for that object, then, when it commits, Magma will have the old/new key.
- Chris
2009/5/12 Hilaire Fernandes hilaire@ofset.org:
I am not sure about this situation.
I have a MagmaCollection with an index elaborated from a lexical term object. The index use the hash value of this lexical term object
The lexical terms populate other collections, so these terms can be manipulated independently from the object in my MagmaCollection.
Now I am wondering which action I should take when a lexical term is edited in a way its hash value is modified. Should I iterated in the MagmaCollection the objects referring to this same term and send a noteForOldKeys: message ?
Hilaire
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma