Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question on db-migrate up #23

Open
opike opened this issue Sep 14, 2017 · 2 comments
Open

question on db-migrate up #23

opike opened this issue Sep 14, 2017 · 2 comments

Comments

@opike
Copy link

opike commented Sep 14, 2017

Is it possible to run "db-migrate up" on a single file?

I tried node_modules/.bin/db-migrate up 20170908035335-disputes
(where there's a file migrations/20170908035335-dispuates.js) but db-migrate still attempts to run all the migration files in migrations/.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@wzrdtales
Copy link
Member

wzrdtales commented Sep 15, 2017

No it is not and it is clearly not intended to ever support this, as this is clearly against what migrations are. Migrations are not a replacement for sql scripts, they are intended to version control your schema which implies that it never executes off the chain within the same context.

@matticus1181
Copy link

It looks like it does support running a single migration. From the docs:db-migrate up 20150207135259-myFancyMigration

I'm trying to figure out how to run a single migration that's in a scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants