Duplicated 'migrations' table when using schemas about pg HOT 6 OPEN

I ran into the same issue. What it ended up being for me was that my first migration script was creating the schema that I had configured in my schema field in database.json. Because this schema didn't exist until the first migration was run, the migrations table was created in the public schema the first time I ran db-migrate. On the next run, another migrations table was created in my configured schema, but because it is empty, all of my migrations are run all over again.

from pg.

I think it would be good if db-migrate-pg just checked if the schema specified in database.json exists, and if not then it should be created before the actual migrations start.

from pg.

@EyMaddis No you can't configure it via the database.json and currently you can't, but on the latest master branch there already is the rc config included which will allow you to do so via a .dbmigraterc config. About the behavior, this is really strange, can you provide me a full example to reproduce this?

from pg.

Bump. Completely same behavior as @justinnguyen describe. Any progress on that?

from pg.

Bump. I hit the same issue as @justinnguyen and @igorlysak hit.

from pg.

Any update on when the above PR will be merged in?

from pg.