The "recommended" way would be to use ConfigurationOfGarageGlorp and use Garage's PostgreSQL driver (which is a fork from the PostgresV2 one). However I couldn't tell whether there is a difference (both in performance and/or features) between them because the codebase moves a glaciar speed; I'm aware of some users that prefer to stick with the old driver (pgV2) instead of the Garage alternative (which isn't much maintained either), since both preserve the API and different Glorp drivers (adapters) corrects any difference. In the booklets Stef published days ago there is a link to the one of Glorp I wrote, there is a snippet of the "recommended" way to load Glorp using the Garage configurations. Which one you choose is up to you. Regards! Esteban A. Maringolo 2017-05-16 6:58 GMT-03:00 Sven Van Caekenberghe <sven@stfx.eu>:
I am bringing my Reddit example back up to date (https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b532...) for an upcoming Pharo Booklet.
I used to depend on and load Glorp+PostgreSQL in my Configuration as follows:
spec project: 'Glorp' with: [ spec className: 'ConfigurationOfGlorp'; versionString: #stable; repository: 'http://www.smalltalkhub.com/mc/DBXTalk/Configurations/main' ].
spec project: 'PostgresV2' with: [ spec className: 'ConfigurationOfPostgresV2'; versionString: #bleedingEdge; repository: 'http://www.smalltalkhub.com/mc/PharoExtras/PostgresV2/main' ].
spec package: 'GlorpDriverPostgreSQL' with: [ spec repository: 'http://www.smalltalkhub.com/mc/PharoExtras/PostgresV2/main'; postLoadDoIt: #postLoadGlorpPostgresNativeDriverDBXTalkPharo; requires: #( 'Glorp' 'PostgresV2' ) ].
This works fine in Pharo 6 now.
My first question is, is this the 'correct' way of loading Glorp+PostgreSQL ? Do I get the latest, maintained code this way ?
My second question is, why is #stable not available for Pharo 6 for PostgresV2, what should be done to fix this and could someone add it ?
Thx,
Sven