2017-08-14 9:07 GMT-03:00 Herby Vojčík <he...@mailbox.sk>: >> Garage is not maintained as people started developing the alternative >> UDBC drivers, that share the same spirit at the end. I do not know if >> they share the same API though. > > I did not know. So I should use ConfigurationOfGlorpSQLite instead of > ConfigurationOfGarageGlorp as my dependency?
In the Glorp booklet these are the instructions to install SQLite: Gofer it smalltalkhubUser: 'TorstenBergmann' project: 'UDBC'; configuration; load. (Smalltalk at: #ConfigurationOfUDBC) loadBleedingEdge. Gofer it smalltalkhubUser: 'DBXTalk' project: 'Garage'; configurationOf: 'GarageGlorp'; load. (Smalltalk at: #ConfigurationOfGarageGlorp) project stableVersion load. Gofer it smalltalkhubUser: 'DBXTalk' project: 'Glorp'; package: 'Glorp-SQLite3'; load. >> About Glorp, I will let Esteban Maringolo ask :). > It seems from other responses that Glorp is fine. :-) Glorp was updated in Pharo last year from the latest version in Cincom Public Repository, although a year might seem like a lot, it isn't much because Glorp is mostly in "maintenance", and the ORM domain isn't a moving target anymore. What we're still lacking is better database drivers, not for Glorp which supports many, but in terms of low level connectivity. I really liked the idea of an unified driver layer the way UDBC was taking, unfortunately this was put to a halt. Maybe we should focus on having good reliable native drivers instead of trying to support all and end up having incomplete support for only a few. Regards! Esteban A. Maringolo ps: I'm currently not doing any RDBMS on Pharo, and that's why I'm not "updating" Glorp with minor/usability changes, but I'm using Glorp with SQLite in VW, so in the future I might update Pharo's port if there are changes. However those update must be manual, since Glorp isn't coordinated to be portable as Seaside or other projects are.
