Re: [Pharo-users] Mongo cache vs database objects

On 27 Nov 2013, at 2:57 , Sabine Knöfel wrote: > ok:-) > > btw and ot: > http://adam-fletcher.co.uk/howtobegerman/ > recommend! Haha, completely OT, but just the description brought back a memory from a class trip to Lübeck 15 years ago… Ater I decided to disobey the red man, an old lady rema

Re: [Pharo-users] Mongo cache vs database objects

In general, any comments/observations/additions are welcome of course! Latest version of the docs are always online and built by the pharo CI. On Nov 27, 2013, at 10:48 AM, Norbert Hartl wrote: > Ah, the other Johan! It is good to know because I did some changes to > MongoTalk so I see what I

Re: [Pharo-users] Mongo cache vs database objects

On Nov 27, 2013, at 9:42 AM, Norbert Hartl wrote: >> And the question coming along with this: >> How long does the cache keeps objects/when are they reseted (except the VORepository current reset)? >> If I would never take a new image and never make a reset, would all objects >> remain in

Re: [Pharo-users] Mongo cache vs database objects

On Nov 27, 2013, at 10:48 AM, Norbert Hartl wrote: >> This was the post FROM Johan about the documentation: >> http://forum.world.st/Cleaning-up-Voyage-Documentation-td4723834.html >> >> LOL now, after writing the answer I understand the joke ;-) (of Johan, from >> johan) >> > Ah, the other J

Re: [Pharo-users] Mongo cache vs database objects

On Nov 27, 2013, at 10:16 AM, Norbert Hartl wrote: >> Perhaps your answer is also interesting for the documentation of Johan. >> > Uh? I’ve never seen a documentation about Johan. That is a nice idea! I was > always thinking about how to use him! How to use me is easy apparently, just ask my

Re: [Pharo-users] Mongo cache vs database objects

ok:-) btw and ot: http://adam-fletcher.co.uk/howtobegerman/ recommend! On Wed, Nov 27, 2013 at 2:49 PM, Norbert Hartl [via Smalltalk] < ml-node+s1294792n4725604...@n4.nabble.com> wrote: > > Am 27.11.2013 um 14:28 schrieb Sabine Knöfel <[hidden > email]

Re: [Pharo-users] Mongo cache vs database objects

Am 27.11.2013 um 14:28 schrieb Sabine Knöfel : > Hi Norbert, > > ooh sorry, it was absolutely NOT my intention to critisize your explanation > I wanted to say it is complicated for my small brain ;-) I am very happy > about your quick answer which helped me finding a solution for my problem!

Re: [Pharo-users] Mongo cache vs database objects

Hi Norbert, ooh sorry, it was absolutely NOT my intention to critisize your explanation I wanted to say it is complicated for my small brain ;-) I am very happy about your quick answer which helped me finding a solution for my problem!!! sorry! This was the post FROM Johan about the documentati

Re: [Pharo-users] Mongo cache vs database objects

Am 27.11.2013 um 14:05 schrieb Sabine Knöfel : > Hi Norbert, > > thank you very much for the clarification. > > I had to read it several times but now I understand and I know what to > change in my model for this (something with references to objects which have > been deleted by the user).

Re: [Pharo-users] Mongo cache vs database objects

Hi Norbert, thank you very much for the clarification. I had to read it several times but now I understand and I know what to change in my model for this (something with references to objects which have been deleted by the user). Perhaps your answer is also interesting for the documentation of

Re: [Pharo-users] Mongo cache vs database objects

Am 27.11.2013 um 13:20 schrieb Sabine Knöfel : > Hi Esteban, all, > > I work with mongo daily an it works fine, I am very happy with it. > > As you told me, with >>> VORepository current reset. > I can force re loading all objects from database and resetting the cache > completely. > This is he

[Pharo-users] Mongo cache vs database objects

Hi Esteban, all, I work with mongo daily an it works fine, I am very happy with it. As you told me, with >>VORepository current reset. I can force re loading all objects from database and resetting the cache completely. This is helpful for development eg. after changing the magritte descriptions.