It wasn't your mistake, there was an error that leaked into the script
because of one of those "last minutes changes". My bad.

However, as I told you in the #databases channel, but I'm replying
here so everyone else knows, Glorp supports SQLite3 as one of its
platforms and actually this port brings many corrections and
modifications for such particular platform, but the SQLite3 driver in
Pharo 5 isn't fully functional (aka, doesn't work) yet because of
changes in the FFI of Pharo 5.

Pierce, the developer of NB SQLite3 driver
<http://www.samadhiweb.com/tags/sqlite> is helping us with getting the
SQLite3 driver back to Pharo 5.

This issue can be followed "live" in the
https://pharoproject.slack.com/messages/databases/ channel.

Regards!

Esteban A. Maringolo


2016-05-31 15:08 GMT-03:00 Alistair Grant <[email protected]>:
> Hi All,
>
> Thanks to Estaban and everyone involved in making Glorp available in
> Pharo 5.0.
>
> I'm trying to work my way through the examples in the Glorp book
> (https://ci.inria.fr/pharo-contribution/job/PharoBookWorkInProgress/lastSuccessfulBuild/artifact/book-result/Glorp/Glorp.pdf)
> but, embarrassingly, haven't got past the first step.
>
> My understanding from the book is that I load Glorp with:
>
> Metacello new
>         smalltalkhubUser: 'DBXTalk' project: 'Garage';
>         configuration: 'GarageGlorp';
>         version: #stable;
>         load.
>
> I've also tried loading the Glorp package with:
>
> Gofer it
>         url: 'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main';
>         configurationOf: 'Glorp';
>         loadStable
>
> but still aren't able to execute the first command in the book:
>
> GAGlorpAccessor beDefaultGlorpDriver
>
> since GAGlorpAccessor isn't in the image, or, later on:
>
> accessor := GarageDatabaseAccessor forLogin: login.
> accessor login.
>
> since GarageDatabaseAccessor also isn't in the image. (I was able to
> create the login object).
>
> What is the required sequence of Montacello / Gofer loads to be able to
> use Glorp with SQLite3?
>
> Thanks,
> Alistair
> (who is sure he has missed the obvious)
>
>

Reply via email to