Have a way to run migrations on an arbitrary database.

[Shuhao]

I have a :memory: sqlite3 database for tests. I want to be able to run migrations on that database without essentially copying RunMigrations in my code base.

[Liam Staskawicz]

Is it possible to create a DBConf that describes your test database, and use that for testing?

[Shuhao]

I suppose.. After looking into exposing that API and not having too many success, I setup a test db file.

[Shuhao]

Where is the db path relative to? Where you run the command? Where the package is? I'm having trouble with that.

[Liam Staskawicz]

I believe the path should be relative to the executable - it's probably simplest to pass an absolute path if you're having trouble. That should be the path to the directory containing your dbconf.yml and migrations dir.

[Liam Staskawicz]

Were you able to get this working? If so, I'd like to close out the issue & pull request. Thanks.

[Shuhao]

Sorry for the long delayed response: I still think it is necessary to be able to run migrations on arbitrary database as a dbconf may not be sufficient.

Unittests are supposed to be independent of each other. If I have multiple packages that depend on the same database, I might get some weird global state issues when I run go test ./... as they tend to run in parallel.

In each test suite's setup I can create a new database connection to a different databse (in sqlite3 it would be :memory:) to avoid any issues with global state, but I cannot run migrations to an arbitrary connection.

Also things like :memory: is just a lot faster, and I must hold on to that connection (specifying :memory: in dbconf just won't work).

[Shuhao]

Any updates on this? I still would like to do this as it will speed up and simplify my unittesting code...

[Parker M]

Function to migrate specific database.

Fixes #28

→ <<cset 1ff4053a43a4>>