March 2, 2017
8:58 p.m.
Hi Hilaire, I do not understand well your problem. Which query do you want to implement? cheers! Esteban
On 2 Mar 2017, at 21:32, Hilaire <hilaire@drgeo.eu> wrote:
Problem seems related to object identity, which imply a primitive call in Object>== message. Si I guess it may not let a chance to Voyage to resolve to the the real object but stay at it 'proxy-oid-whatever' stuff.
Non working code looks like:
myObjectInRepo select: [ :each | someObjects includes: each anAttribute "the one Voyage should fetch"]
I guess implementing = and hash in the anAttribute class will resolve the issue, but it will be slower, and an uneeded feature.
Any alternative idea?
Hilaire
-- Dr. Geo http://drgeo.eu