Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Latest" docs show `callback` arg to `up()` but `db-migrate create` does not

See original GitHub issue

Creating a migration with db-migrate create yields up (db) rather than up (db, callback) – this is inconsistent with the docs.

I’m running 0.10.0-beta.20 from NPM

Issue Analytics

State:
Created 7 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

wzrdtalescommented, Nov 2, 2016

Cool thing! Gonna have a look later

0reactions

chadfurmancommented, Nov 1, 2016

@wzrdtales how’d I do? ❤️

Top Results From Across the Web

Usage - db-migrate - Read the Docs

node-db-migrate will create a node module within ./migrations/ which contains the following two exports: exports.up = function (db, callback) { callback(); }; ...

db-migrate - npm

All you have to do is populate these, invoking callback() when complete, and you are ready to migrate! For example: $ db-migrate create...

Sequelize.js: how to use migrations and sync - Stack Overflow

Generating the "first migration". In your case, the most reliable way is to do it almost manually. I would suggest to use sequelize-cli...

Active Record Migrations - Rails Edge Guides

Migrations are a feature of Active Record that allows you to evolve your database schema over time. Rather than write schema modifications in...

Flyway by Redgate • Database Migrations Made Easy.

Repeatable migrations have a description and a checksum, but no version. ... Flyway will automatically pick up any new SQL migrations as long...