Hi there,
I'm using this MaDatesAndTimesIndex which is a kind of MaKeywordIndex but to store N dates per element. When I set a halt in the message the index send to elements I saw it halting when an element is added. If I change values, with impact on the values of the index, in a previously stored element, I'm not seeing it halting.
Magma is not automatically maintaining that kind of index? What one should do to achieve that?
thanks,
Sebastian Sastre
When you change indexed value, you need to notify Magma with the noteOldKeysFor: message. There is some info in the Magma wiki.
Hilaire
Le mercredi 20 février 2008 à 19:02 -0300, Sebastian Sastre a écrit :
Hi there,
I'm using this MaDatesAndTimesIndex which is a kind of MaKeywordIndex but to store N dates per element. When I set a halt in the message the index send to elements I saw it halting when an element is added. If I change values, with impact on the values of the index, in a previously stored element, I'm not seeing it halting.
Magma is not automatically maintaining that kind of index? What one should do to achieve that?
thanks,
Sebastian Sastre
When you change indexed value, you need to notify Magma with the noteOldKeysFor: message. There is some info in the Magma wiki.
Hilaire
Oh I get it. But I was thinking Magma was doing that automatically. But if so I don't get why Magma is using the write barrier,
cheers,
Sebastian
magma@lists.squeakfoundation.org