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 <sabine.knoefel@gmail.com> 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.h... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.