Hi Guille, I had a short look at Garage [1]. Nice initiative!
Looks like using a file is not supported for the SQLite3 backend in Garage: GADriver fromConnectionString: 'sqlite3://file://C:/temp/test.db' GADriver fromConnectionString: 'sqlite3://C:/temp/test.db' Maybe GASqlite3Driver>>fromConnectionString: could be adopted, but the conversion to a Zn URL already removes some stuff. (Ab)using the schema in the URL as a driverID is nice - but prevents the use of file:// schema. How can one construct a file db? Also I do not understand: while "Garage-Postgres" uses the Postgres project PostgresV2 as a backend the "Garage-Sqlite3" does not use NBSqlite3 or SQlite3 projects as backend. So "GASqlite3FFI" copies many methods of the original NBSQLite3 project from Pierce and myself and is therefore like an own fork now. Also the name FFI is misleading as it uses NativeBoost instead of FFI ... Also it would be good if the project would be layered, we could have a "Garage-Core" and "Garage-Tests-Core" with "Garage-Mysql" and "Garage-Tests-Mysql" for the fixtures. The idea is always to be able to load runtime code without tests for production code. Thanks Torsten [1] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-May/019192.html
