Voyage

I'm trying to load Voyage for MongoDB and I'm having great difficulty. The docs seem to be out of date. What are the current instructions for doing this? The docs also refer to "Configurations Browser" in World Menu/Tools, but there is no longer any such thing. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Voyage

... select “proceed”. That will allow voyage to load properly. Cheers, Esteban > On 2 Dec 2018, at 12:39, Sanjay Minni <sm@...> wrote: > > I am unable to load Voyage-Mongo and Voyage-Memory in Pharo 7.0.0rC1 > > tried using the scipt below and also thru the Catalog Browser...

Voyage

Le 16/11/2018 à 02:02, horrido a écrit : > I'm trying to load Voyage for MongoDB and I'm having great difficulty. The > docs seem to be out of date. > > What are the current instructions for doing this? > > The docs also refer to "Configurations Browser" in World Menu/Tools, but > there is...

Voyage

I am unable to load Voyage-Mongo and Voyage-Memory in Pharo 7.0.0rC1 tried using the scipt below and also thru the Catalog Browser entries for Voyage any pointers CyrilFerlicot wrote > Le 16/11/2018 à 02:02, horrido a écrit : >> I'm trying to load Voyage for MongoDB and I'm having...

Voyage Timeout

Hi, When I configure a production image with command st handler as following: pharo myImage st --save --quit configureMyImage.st I notice at image start up, a Socket timeout error. In the configureMyImage.st script, among other things, I open a singleton Voyage repository. I added a 5s...

Voyage

... an > old API: #ifNotNilDo: that does not exists anymore in Pharo. > You are probably seen something like this: > > > > > (And this is a bug) > Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, > then save and select “proceed”. > > That will allow voyage to...

Voyage

...) >> Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, >> then save and select “proceed”. >> >> That will allow voyage to load properly. >> >> Cheers, >> Esteban >> >> >> >>> On 2 Dec 2018, at 12:39, Sanjay Minni &lt; > >> sm@ > >> &gt; wrote: >>> >>> I...

Voyage

...: #ifNotNilDo: that does not exists anymore in Pharo. > > You are probably seen something like this: > > > > > > > > > > (And this is a bug) > > Anyway, while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, > > then save and select “proceed”. > > > > That will allow voyage to load properly...

Voyage hang

From a production image, built from script with the voyage configuration as: >"External PROJECTS dependencies" >spec project: 'voyage' with: [ > spec > className: 'ConfigurationOfVoyageMongo'; > repository: 'github://pharo-nosql/voyage:master/mc'; > versionString: #stable...

QCMagritte & Voyage?

All, I'm currently trying to wrap my head around QCMagritte. So far it seems to include most of what I need. I'm not sure though how/where to integrate a persistency layer (i.e. Voyage in this case). I'm either missing some place to activly take control and do saving/upgrading or any callback when objects/collections have been changed. Any pointers or sample code? Thanks, Udo

Voyage

On Sun, Dec 2, 2018 at 4:46 PM Esteban Lorenzano <estebanlm@...> wrote: > > So we just need to change the dependency. Cool :) > > In fact the dependency was already changed by Norbert! The problem is that we need a new release of mongotalk and to update the release used by Voyage :) So I cannot help here since I'm not part of pharo-nosql. -- Cyril Ferlicot https://ferlicot.fr

Voyage

..., while we fix this, you can replace #ifNotNilDo: for #ifNotNil:, >>> then save and select “proceed”. >>> >>> That will allow voyage to load properly. >>> >>> Cheers, >>> Esteban >>> >>> >>> >>>> On 2 Dec 2018, at 12:39, Sanjay Minni &lt; >> >>> sm@ >> >>> &gt; wrote...