Create migrations table in specified schema#287
Conversation
In postgres, if you create a migrations table in one schema of your database, and then try to use this for migrations in another schema, it will not create the migrations table in the second schema which will prevent any migrations from running on that schema. This creates the migrations table in that second schema when the schema parameter is specified.
|
NB the build only failed on iojs-3 and it failed there because it failed to build the native modules this module depends upon. |
|
Yeah I know about io.js - 3. I'm going to remove it from the builds until it gets fixed, haven't pushed my changes of yesterday already.... See also this note concerning this: |
There was a problem hiding this comment.
Please don't use async, I'm currently working on kicking this dependency out of the project. The whole project will rely on promises in the future.
I have ported your changes to use bluebird in the master repo, but please consider this for future contributions.
[Bugfix] Create migrations table in specified schema
|
Considered as bugfix, releasing as patch 0.9.19 |
|
Awesome! Thanks so much! |
|
Just waiting for the CI first, oh ok, its done already..., faster as usual. Published! |
|
💥 Thanks, again! |
|
No problem, thanks for contributing! |
2 participants
In postgres, if you create a migrations table in one schema of your database,
and then try to use this for migrations in another schema, it will not create
the migrations table in the second schema which will prevent any migrations
from running on that schema. This creates the migrations table in that second
schema when the schema parameter is specified.