Fails with preceeding/existing migrations

[downzer0]

When creating a second migration and attempting to migrate up to add it, the task fails because the first migration was already run. It seems to be running (and failing) rather than skipping previously successful/complete migrations.

I tried with the --no-check-order option, but got the same results.

I've got two migrations currently, one was created and run successfully a while ago. The second was created recently. When running the second, it sees the first and fails. Checking the pgmigrate database table does in fact show the first/initial migration there. Timestamps match.

I was hesitant to file an issue because this seems like user-error, but searching StackOverflow and the web doesn't turn up similar findings. Am I doing something wrong, or is this a legit bug?

> pg-migrate up

> Rolling back attempted migration ...
Error: Not run migration 1491784040558_create-table-users is preceding already run migration 1491784040558_create-table-users.js

[dolezel]

Can you please provide output for ls -la in migrations folder and select * from pgmigrations;?
Thanks

[jitendrapawar]

Hello @dolezel ,

I am also getting the same error, but I got to know why we are getting this issue.

Actually it was because of I dont have a migration file which is already executed on database. This scenario arises because we are using shared database for our local environment. We dont have a database locally. So one of team member created a migration & execcuted that on database but that migration file is not yet shared with the team(as merge request is not approved yet)

So can you please let us know if can use any other option in node-pg-migrate to avoid this error.

[dolezel]

Using --no-check-order will disable check for migration order (see)
But I can only advise you to use different DB for each developer, or at least for each feature. You can't be even sure if something goes wrong (with almost anything), if it is bug in current branch or done by another developer working on some other feature...

[jitendrapawar]

Yes, I agree on that.
But I checked with -no-order-check, it didn't worked

[dolezel]

It has to be run with double dashes for parameters to be passed through npm:
e.g. npm run migrate up -- --no-check-order

[downzer0]

Woah sorry I lost track of this! Looks closed, and I haven't run into the issue again. Thanks for being attentive.

[titarenko]

npm run migrate up -- --no-check-order – worth mentioning in docs

[mieradi]

Thanks for all the info!

Are there any risks when running -- --no-check-order?