+1
> Le 26 janv. 2017 à 16:10, stepharong a écrit :
>
> This is great
> I would love to know what is your application and we should add it in the
> success stories.
>
> Stef
>
>> Hi!
>>
>> I’m close to deploy a web service using Pharo with Voyage and MongoDB. I
>> have
This is great
I would love to know what is your application and we should add it in the
success stories.
Stef
Hi!
I’m close to deploy a web service using Pharo with Voyage and MongoDB. I
have been playing with it and everything works ok with a single Pharo
image.
Couple of days ago I
> On 25 Jan 2017, at 22:39 , Alejandro Infante
> wrote:
>
> Cool! Thanks for the answers!
>
> Norbert mentions something interesting about references.
> I have found that even though on each query mongo get the up-to-date version
> of the objects, it does not
Cool! Thanks for the answers!
Norbert mentions something interesting about references.
I have found that even though on each query mongo get the up-to-date version of
the objects, it does not install the proxies to look for the up-to-date
versions of the references of the queried object.
I
> On 25 Jan 2017, at 01:30, Alejandro Infante
> wrote:
>
> Hi!
>
> I’m close to deploy a web service using Pharo with Voyage and MongoDB. I have
> been playing with it and everything works ok with a single Pharo image.
>
> Couple of days ago I started
Hi,
> Am 25.01.2017 um 01:30 schrieb Alejandro Infante
> :
>
> Hi!
>
> I’m close to deploy a web service using Pharo with Voyage and MongoDB. I have
> been playing with it and everything works ok with a single Pharo image.
>
> Couple of days ago I started
Hi!
I’m close to deploy a web service using Pharo with Voyage and MongoDB. I have
been playing with it and everything works ok with a single Pharo image.
Couple of days ago I started questioning myself about how voyage behaves when
you have multiple pharo images using the same mongo database