pharo-rdbms / garage Goto Github PK

to allow setUp of tests (to create database, tables, etc.)

Sorry, but I do not get it. I tried to make it run here in an Pharo 8.x
And I think I quite suceeded, but I'd to patch the stuff.

So who's the maintainer, and how can I get in touch with him?

Hi,

I tried Garage but I get this error while I connect: Error: FATAL: SASL authentication is not supported in protocol version 2

Do you have any pointer on why this error can happen?

I didn't find any documentation with a quick search and there doesn't appear to be any objects mentioning SSL in Garage-Mysql. Is it possible to connect through SSL to MySQL?

Since the source code of all subclasses is doing basically the same.

I think using ROLLBACK query to rollback a query is standard and followed by all major DBMS.

Fixing #14 before would help.

Additionally, GAMysqlDriver>>#driverId source code is exactly the same as GAMysqlDriver class>>#driverId.

I propose to simply remove:

• GAPostgresDriver>>#driverId
• GAMysqlDriver>>#driverId

Maybe #basicExecute: should be deprecated and replaced by a method named #basicQuery:.

They should be updated to latest pharo

Having a broken copy of SQLite3 code inside garage is kind of useless. I would like to see garage contain only adapters and references to external database drivers to allow people to pick and choose what drivers they would like to run while still providing a common interface like PHP PDO, ODBC, JDBC, etc.

It would be great to have a release of Garage to be able to point to a stable version instead of a branch that might break in the future.

Is a release planned?

We should add jobs for Oracle+opendbx, once opendbx is fixed to work on UFFI.

Here is a project to install oracle in travis:

• https://github.com/cbandy/travis-oracle

Today, all jobs are paying a bit the prices of other jobs because we need to make an homogeneous infrastructure to run the tests depending on the platform. For example:

• all osx jobs are taking ~5 minutes because they require updating brew and installing mysql. This happens because osx slaves do not come with mysql installed by default

if [[ $TRAVIS_OS_NAME == "osx" ]]; then brew update > /dev/null && brew install mysql && mysql.server start; fi

• all linux jobs are reinstalling sqlite3 even for non-sqlite jobs

if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
    sudo apt-get autoremove sqlite3;
    sudo apt-add-repository -y ppa:travis-ci/sqlite3;
    sudo apt-get -y update;
    sudo apt-cache show sqlite3;
    sudo apt-get install sqlite3=3.7.15.1-1~travis1;
    sudo sqlite3 -version;
fi;

• all osx jobs are also making a by-hand startup of postgres

if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
    export PG_DATA=$(brew --prefix)/var/postgres;
    rm -rf ${PG_DATA} && initdb ${PG_DATA} -E utf8;
    pg_ctl -w start -l postgres.log --pgdata ${PG_DATA};
    createuser -s postgres;
    cat postgres.log;
fi;

We should make that specific scripts for each database are run for each database. And try to do it outside the .travis.yml file because it starts to get too complicated.