Hi Esteban,
sorry but I need your help again.
I succeeded in re-writing all my code to use voyage and can save all my
model now. Great!
Now I was experimenting with it and I have an Image freeze which should not
occur in production;-).
Situation:
I created one Person with two trips. Trip point
Hi Sabine,
yes... I have found that problem time to time too.
The way to solve it in mongo is to allow the collection to take dead references
as "valid missing content". Of course, this is a dangerous feature, and that's
why is not enabled by default.
To enable it, you need to add a property
Hi Esteban,
thank you for your quick response.
I already had the >>enableMissingContent method in the mongoContainer (see
fileout).
I was trying with a new Image and it worked!
In the old image, I debugged into and the Image froze in >>basicNew in
VOLazyProxy>>repository: aRepository objectClas
I've been bitten by this too.
This is when the "image" concept get counterproductive if you didn't
commit all your code changes. :-/
Esteban A. Maringolo
Hi Esteban,
til now, it did not come back to me.
Can you reproduce it with a fresh image?
Btw I am saving my image now each hour or so...
Sabine
On Sat, Aug 31, 2013 at 5:46 PM, Esteban A. Maringolo [via Smalltalk] <
ml-node+s1294792n4705953...@n4.nabble.com> wrote:
> I've been bitten by this
2013/8/31 Sabine Knöfel :
> Hi Esteban,
>
> til now, it did not come back to me.
> Can you reproduce it with a fresh image?
The image freezed, but fortunately with a LOT of patience I was able
to type a character every once in a while. So I could write an
smalltalk expression that after being eval
