Hi Tommaso, that might be a bug… which version are you using? if latest, can you fill a bug here: https://github.com/estebanlm/voyage/issues (so I do not forget it)?
thanks, Esteban > On 08 Mar 2016, at 16:25, Tommaso Dal Sasso <tommaso.dalsa...@gmail.com> > wrote: > > Hi, > > thanks for your answer, I also tried with One>>mongoContainer, but sadly that > does not solve the issue. > I think it works in your case because you have the One object cached from the > previous query, but if you inspect the "link" field, it should be nil. > > If you reset the repository connection, it should give the exception again. > > I'll keep trying :-) > Tommaso > > > > On 07/03/16 14:07, Sabine Manaa wrote: >> Hi Tommaso, >> >> you did not define a One>>mongoContainer. I defined it and then it seems to >> work. >> >> Regards >> >> 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <[hidden email] >> <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=0>>: >> Hi, >> >> I am having troubles with Voyage and Mongo. >> I have some Classes that I save in Mongo, say "One", "Two", and "Three". >> All three classes and are voyage roots, so the objects from each class >> are stored in different collections. >> One objects has a reference to Two or Three objects. >> >> The problem arises when I use a Magritte description and define a Mongo >> container to optimize the storage: since each class is stored in its own >> collection, there is no point in storing the #instanceOf attribute as well. >> >> Two>>mongoContainer >> <mongoContainer> >> >> ^ VOMongoContainer new >> kind: Two; >> yourself >> >> If I add this method, when I try to load an object One, I get the >> exception: "KeyNotFound: key #nil not found in SystemDictionary". >> It looks like Voyage is not able to understand the type of the objects >> stored in the collection Two, when loaded from a reference. >> >> Am I missing something? Do I need to specify something more to make it work? >> >> I reproduced the scenario in an image that can be downloaded here: >> https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip >> <https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip> >> >> Do you have any idea? Should I report this on the issue tracker? >> >> Thanks! >> Tommaso >> >> >> >> If you reply to this email, your message will be added to the discussion >> below: >> http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp4882726.html >> >> <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp4882726.html> >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here >> <applewebdata://F53A575C-598C-4B5D-B41C-A90723498F14>. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> >> View this message in context: Re: Voyage, Magritte descriptions, and nil >> exceptions >> <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp4882726p4882948.html> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >
