On 12 Dec 2013, at 14:20, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2013/12/12 Sven Van Caekenberghe <sven@stfx.eu>:
Hi Esteban,
Itâs a mess ;-)
Don't get me started... ;-)
PharoDatabaseAccessor DefaultDriver is NativePostgresDriver.
Not in my installation.
I'm using this to install my Glorp+Postgres combo:
Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorp'; load.
Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPostgresV2'; load.
((Smalltalk at: #ConfigurationOfGlorpDBX) project version: '2.5') load.
((Smalltalk at: #ConfigurationOfPostgresV2 ) project version: '2.1') load.
I'm using ConfigurationOfGlorpDBX instead of ConfigurationOfGlorp because somebody told me so several months ago when I asked. ConfigurationOfGlorp seems really outdated.
If you can send me the NativePostgresDriver class I'll test if that solves the problem.
The class NativePostgresDriver is in a package called GlorpDriverPostgreSQL. It seems to have come from MCSqueaksourceRepository location: 'http://squeaksource.com/PostgresV2' user: '' password: â' I have this version in my (older) image (it seems to be the latest): Name: GlorpDriverPostgreSQL-GuillermoPolito.3 Author: GuillermoPolito Time: 12 June 2011, 1:33:54 am UUID: 770cafdc-c5e4-4f39-a52d-63e4b3aee6d8 Ancestors: GlorpDriverPostgreSQL-MarianoMartinezPeck.2 Sven
Now I see the 2.5 spec of ConfigurationOfGlorpDBX tries to load the NativePostgresDriver... but from the 1.0...
Anyway, other advantages of this driver are that you can go from one machine to another, over ssh, double-check with psql, You can even go from your dev machine / image to your production server db (over ssh) over the internet â¦
I know, I rather go with self-contained solutions whenever possible.
Regards,