Re: [Pharo-users] Voyage and instances retrieving

I'll make a test case to illustrate the issue. Hilaire Le 06/03/2017 à 19:05, Esteban Lorenzano a écrit : >> Ah, sorry I was not clear enough in my introduction. Obviously, I >> removed all =/hash overrides on the involved objects and it is therefore >> an orthogonal issue (that's why I first

Re: [Pharo-users] Voyage and instances retrieving

> On 6 Mar 2017, at 18:56, Hilaire wrote: > > Ah, sorry I was not clear enough in my introduction. Obviously, I > removed all =/hash overrides on the involved objects and it is therefore > an orthogonal issue (that's why I first resolved the other issues > first). Or did you

Re: [Pharo-users] Voyage and instances retrieving

Ah, sorry I was not clear enough in my introduction. Obviously, I removed all =/hash overrides on the involved objects and it is therefore an orthogonal issue (that's why I first resolved the other issues first). Or did you mean something I did not understand in your previous message? Hilaire Le

Re: [Pharo-users] Voyage and instances retrieving

just as a side note: you must NEVER do a hash based in an attribute that might change. You will screw not just Voyage but all collections where your object is stored (except Array). Esteban > On 6 Mar 2017, at 18:34, Hilaire wrote: > > Le 03/03/2017 à 18:09, Hilaire a

Re: [Pharo-users] Voyage and instances retrieving

Le 03/03/2017 à 18:09, Hilaire a écrit : > I will try to dig for more clues. Now that I clarified the issues regarding duplicated entries and Date. I took another look to this problem. After reset of the repo, to test for sure Voyage correctly retrieves the attributes, I face the same issue

Re: [Pharo-users] Voyage and instances retrieving

Some more clues: in my application if I go in other part where these attributes are used for some simulation, the attributes are resolved as expected. Then when I go back the other part the select is working. On more hints: the attribute collection seems to resolve fine, so proxy is working,

Re: [Pharo-users] Voyage and instances retrieving

> On 3 Mar 2017, at 17:24, Hilaire wrote: > > I don't understand why I should use a query! > I already have an instance of the object fetched from the repo but its > attributes are not resolved when read from an iterator block: I can't > pick up the one I want. mmm,

Re: [Pharo-users] Voyage and instances retrieving

I don't understand why I should use a query! I already have an instance of the object fetched from the repo but its attributes are not resolved when read from an iterator block: I can't pick up the one I want. These attributes are not root, to the contrary to what I wrote initially. Hilaire Le

Re: [Pharo-users] Voyage and instances retrieving

> On 3 Mar 2017, at 12:17, Hilaire wrote: > > Hi Esteban, > > I could, but I don't understand why the attribute does not resolve to an > object equals to the other one in memory. if you have objects in memory you can do MyRoot selectAll select: [ :each |

Re: [Pharo-users] Voyage and instances retrieving

Hi Esteban, I could, but I don't understand why the attribute does not resolve to an object equals to the other one in memory. If I add an inspect to the attributes, it resolves correctly and code work as expected: myObjectInRepo select: [ :each | each anAttribute inspect. someObjects

Re: [Pharo-users] Voyage and instances retrieving

> On 3 Mar 2017, at 10:00, Hilaire wrote: > > Hi Esteban, > > I want to select some objects with code Smalltalk selectors, as bellow. why? you cannot transform that into a mongo query? something like: myObjectInRepo select: [ :each | (each at: ‘attribute’) in:

Re: [Pharo-users] Voyage and instances retrieving

Hi Esteban, I want to select some objects with code Smalltalk selectors, as bellow. In the code bellow, myObjectInRepo is already fetched from the repo (so it is in the image), but the select: return an empty list, but it should not be empty. myObjectInRepo select: [ :each | someObjects

Re: [Pharo-users] Voyage and instances retrieving

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

[Pharo-users] Voyage and instances retrieving

Hi, When iterating, with Smalltalk selectors, an object persisted in a repository, some of its attributes (I guess because root for other collection) are not resolved as expected at iteration. The Smalltalk iteration does not work, returning empty result. Fetching the whole model in memory will