Hi Esteban,
this would be fine!
A few minutes ago, I wrote another thread here with some questions about
memory. And after sending it now I got the following message from pharo
"Space is low
Warning! Pharo is almost out of memory. "
So, if you could tell something about memory usage in you
On Aug 13, 2013, at 4:58 PM, Sabine Knöfel wrote:
> Hi Esteban,
>
> thanks, this works fine now!
>
> You also answered my next question how to define an attribute as transient
> -> with VOMongoTransientDescription :)
>
> Your blog posts
> http://smallworks.com.ar/web/blog?_k=c9RiCz1d5w-0XSbp
Hi Esteban,
thanks, this works fine now!
You also answered my next question how to define an attribute as transient
-> with VOMongoTransientDescription :)
Your blog posts
http://smallworks.com.ar/web/blog?_k=c9RiCz1d5w-0XSbp
are very helpful to start.
Do you have more information/documentation
Hi Sabine,
Sadly there is no automatic solution for your problem.
I managed to resolve that by hacking the mongo description this way:
Trip class>> isVoyageRoot = true
Day class>> isVoyageRoot = false
VehicleTrip class>> isVoyageRoot = false
Now, the trick is that since the document will be
Hi Esteban,
thank you for the solution with the VOMongoToOneDescription.
This works perfect for me.
I have to come back to the circular references.
I am not sure if this is a bug.
I have the following model:
Trip ->> Day <->> VehicleTrip
One Trip has N Days.
One Day has N VehicleTrips.
The Veh
Hi Sabine,
I'm trying to understand your problem.
As far as I see, you have:
- A set of Countries
- A set of Trips
Why Country is transient?
When you declare an attribute as *transient*, that means its value will not be
persisted, then when you retrieve it again, you will have country = ni
Hi esteban, Thank you for answering. The Problem persists i was waiting for
your answer and it would be great if you could answer my Last Post in the
Forum (how to tell voyage the "boundary"). I am also in vacation now and
back mid of next week. Sorry for the spelling i write from Mobile phone.
Sab
Hi Sabine,
I'm really sorry, I just went on vacations when you sent this mail :(
Is this problem persisting?
Did you reach a solution?
Can I help you with something?
Esteban
On Jul 19, 2013, at 12:56 PM, Sabine Knöfel wrote:
> Hi Esteban,
>
> thanks!
>
> I think the solution of Bernat
:-) For me it would be very useful ;-)
But a hint here in the forum would be enough for the moment to proceed.
Sabine
--
View this message in context:
http://forum.world.st/Voyage-Circular-references-tp4691940p4699971.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
this is a nice case for the tutorial :)
Stef
On Jul 19, 2013, at 12:56 PM, Sabine Knöfel wrote:
> Hi Esteban,
>
> thanks!
>
> I think the solution of Bernat will not be enough for me.
> I added the class methods isVoyageRoot to the root objects (like trip,
> country and so on).
>
> But
Hi Esteban,
thanks!
I think the solution of Bernat will not be enough for me.
I added the class methods isVoyageRoot to the root objects (like trip,
country and so on).
But I have instances which should never be persistent, e.g. the
country I mentioned. The Country has currencies and expense rat
Hi Sabine,
If Bernat help is not enough, I would like to have some more insight on your
problem, so If you can put here a better description of your model and the
problem you are having, I will have a look :)
Esteban
On Jul 19, 2013, at 10:42 AM, Bernat Romagosa
wrote:
> Hi Sabine!
>
> If
Hi Sabine!
If you want an object to be referenced by another, and not embedded in it,
you need to give that object root entity. As a root, the object will have a
collection of its own, and will be referenced by other objects by id. If
the object is not root, it will be embedded inside the referrin
Hi Esteban,
yes, now the Rectangle Example works after doing the reset.
But saving my model still leads to a non responding image because
Voyage is trying to write json for all model stuf deep deep deep and
circular. Perhaps same like:
http://forum.world.st/Voyage-Circular-references-td4691940.ht
Hi Sabine,
Probably you do not missed anything.
Probably I missed to update the voyage configuration :)
can you try doing
VOMongoRepository allInstancesDo: #reset.
before trying again?
Cheers,
Esteban
On Jul 18, 2013, at 6:31 PM, Sabine Knöfel wrote:
> I found this:
> http://smallworks.
I found this:
http://smallworks.eu/web/blog/2013-06-14-voyage-the-adventure
Chapter "Enhancing storage"
But if I add the 3+1 methods to Rectangle, and save it again, the json did
not change.
Did I miss something?
--
View this message in context:
http://forum.world.st/Voyage-Circular-referenc
Hi,
I was working for a while with Mongotalk and started with Voyage today.
I run in exactly the same problem as Bernat. Image non responding.
I tried the star/planet example and it worked. hmpf.
When I debugged into, I recognized that I did not tell Voyage at which
"model bounds" to stop when c
btw the configuration of voyage is outdated in the mongotalk driver (another
thing I need to update, he)
you might want to try manually updating the mongotalk packages.
cheers,
Esteban
On Jun 11, 2013, at 1:39 PM, Bernat Romagosa
wrote:
> Hi Esteban!
>
> Thanks a lot, I tried your code and
Hi Esteban!
Thanks a lot, I tried your code and it's working for me, so the problem
must be somewhere else.
I set up a logger in VOMongoSerializer >> #serialize:description:using: and
I can confirm it keeps jumping back and forth between two related objects,
but I don't really know why...
#new i
Hi,
sorry... I has been running like hell last two weeks.
I posted a reply
http://stackoverflow.com/questions/17039914/how-to-persist-graphs-presenting-circular-references-in-voyage
but sadly no good news... I don't know where is your error. Probably a problem
in your configuration.
I have
Bump?
2013/6/6 Bernat Romagosa
> Hi!
>
> I'm having an issue I don't recall having had about half a year ago when
> trying out Voyage.
>
> In my schema, a *User* has an *instVar* referencing all the *Center*s he
> belongs to, and a *Center* has an *instVar* referencing all of its *User*s,
> so
Hi!
I'm having an issue I don't recall having had about half a year ago when
trying out Voyage.
In my schema, a *User* has an *instVar* referencing all the *Center*s he
belongs to, and a *Center* has an *instVar* referencing all of its *User*s,
so when the Voyage serializer tries to serialize a u
22 matches
Mail list logo
