VORepository current 

should be an instance of VOMongoRepository, not the class 
so, it should not be the same... and it should clean everything.

Esteban

On Sep 19, 2013, at 12:50 PM, Sabine Knöfel <[email protected]> wrote:

> Hi Esteban,
> 
> in my image, the result of 
> VORepository current is ==>> VOMongoRepository
> 
> so, 
> 
> VORepository current reset. 
> it is the same as
> VOMongoRepository reset
> 
> Cheers
> Sabine
> 
> 
> On Thu, Sep 19, 2013 at 12:24 PM, EstebanLM [via Smalltalk] <[hidden email]> 
> wrote:
> Hi Sabine, 
> 
> The right  message to reset is: 
> 
> VORepository current reset. 
> 
> I don't know what "VOMongoRepository reset" does (I need to check it) :P 
> 
> Cheers, 
> Esteban 
> 
> 
> On Sep 19, 2013, at 11:38 AM, Sabine Knöfel <[hidden email]> wrote: 
> 
> > Hi Esteban, all, 
> > 
> > in the mongo/voyage tutorial at ESUG, I understood, that 
> > 
> > "VOMongoRepository reset" can be used instead of 
> > "VOMongoRepository allInstancesDo: #reset". 
> > and the code looks like that ( flush...) 
> > 
> > It seems that I can't - I think, using "VOMongoRepository reset" does _not_ 
> > reset the cache. 
> > So, the objects are not read new from database. 
> > Voyage does not enter the <mongoDescription> methods. 
> > 
> > This is not a problem for me, I can also use "VOMongoRepository 
> > allInstancesDo: #reset", but I want to tell you about that. 
> > 
> > To reproduce I did the following, 
> > 1) read objects from mongo (ClassXXX readAll) 
> > 2) put halt in one of the <mongoDescription> methods 
> > 3 a) do "VOMongoRepository reset" and then (ClassXXX readAll) again -> no 
> > debugger 
> > 3 b) do "VOMongoRepository allInstancesDo: #reset" and then (ClassXXX 
> > readAll) again -> debugger comes up 
> > ==> so, 3a does not work, 3b works 
> > 
> > Regards 
> > Sabine 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120.html
> > Sent from the Pharo Smalltalk Developers mailing list archive at 
> > Nabble.com. 
> >
> 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://forum.world.st/voyage-mongo-reset-vs-allInstancesDo-reset-tp4709120p4709130.html
> To unsubscribe from voyage/mongo reset vs. allInstancesDo: #reset, click here.
> NAML
> 
> 
> View this message in context: Re: voyage/mongo reset vs. allInstancesDo: 
> #reset
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Reply via email to