I think what problem I have... it's a big mess. :) I thought I was using native (Smalltalk) Postgres driver, but in fact I was using the OpenDBX driver, which in turns depends on the native C Postgres library (libqp.dll in Windows).
So now my dependency is not with libpq.so directy, but with OpenDBX. That's my dependency to resolve. The following page, has dead links in how to install it http://dbxtalk.smallworks.com.ar/DBXTalkDrivers/compiling-and-installing-opendbx-native-driver/ Esteban A. Maringolo 2013/12/12 Esteban A. Maringolo <emaring...@gmail.com>: > 2013/12/12 Sven Van Caekenberghe <s...@stfx.eu>: >> Maybe a stupid question, but why not use the PostgresV2 ‘native’ driver. >> This one is network based, it needs no (annoying) libraries, just a socket >> connection ? >> >> And it works perfectly with Glorp. > > I thought I was using it, in fact I load as one of my prerequisites. > > My app only depends on the GlorpSession, which is instantiated as shown > before: > > | login accessor session | > login := Login new > database: (PostgreSQLPlatform new characterEncoding: (config at: > 'encoding' ifAbsent: [ 'utf8' ])); > username: (config at: 'username'); > password: (config at: 'password'); > connectString: (config at: 'hostname') , '_' , (config at: 'database'); > encodingStrategy: (DBXStaticEncoding newForEncoding:'utf8'). > > accessor := DatabaseAccessor forLogin: login. > accessor login. > > The DBXStaticEncoding doesn't seem to instantiate any connection > related classes, but if I remove the line I get the same error. > > But the DefaultDriver of PharoDatabaseAccesor is GlorpOpenDBXDriver, > which is the only direct subclass of Glorp's DatabaseDriver class. I > don't know if there is a DatabaseDriver for Glorp that uses the native > Driver (doesn't seem hard to implement either). > > Now I don't know which path to take. If to properly implement/install > (repo?) the native DatabaseDriver or configure the required external > library. > > Regards.
