Skip to content
Node.js database migration management for Postgresql
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Update all non-major dependencies Docker tags Mar 18, 2019
bin Do not use alias function name (#414) Mar 13, 2019
docs Allow user to specify multiple check constraints when creating table (#… Mar 5, 2019
lib Returning list of run migrations (#411) Mar 7, 2019
test Allow user to pass db client to migration runner (#407) Mar 5, 2019
.babelrc.js Using babel v7 (#331) Sep 26, 2018
.eslintignore - Added typescript migration template (#165) Jan 25, 2018
.eslintrc.js Using babel v7 (#331) Sep 26, 2018
.gitignore Migration tests (#221) Mar 23, 2018
.npmignore
.prettierignore Updated dependencies Jun 25, 2018
.prettierrc.js
CHANGELOG.md Updated changelog Mar 13, 2019
LICENSE Changed author name Jul 20, 2018
README.md Configuring Renovate Nov 30, 2018
index.d.ts Allow user to specify multiple check constraints when creating table (#… Mar 5, 2019
index.js Exporting PgType (#368) Dec 4, 2018
mocha.bootstrap.js Using tests without babel (#291) Jun 29, 2018
mocha.opts
package-lock.json Update all non-major dependencies Apr 15, 2019
package.json Update all non-major dependencies Apr 15, 2019
renovate.json Configure renovate grouping Dec 17, 2018

README.md

node-pg-migrate

Dependency Status devDependency Status NPM version Downloads Licence Known Vulnerabilities Renovate enabled CircleCI

Node.js database migration management built exclusively for postgres. (But can also be used for other DBs conforming to SQL standard - e.g. CockroachDB.) Started by Theo Ephraim, now maintained by Salsita Software.

Looking for v2 docs?

see v2 branch.

Installation

$ npm install node-pg-migrate pg

Installing this module adds a runnable file into your node_modules/.bin directory. If installed globally (with the -g option), you can run node-pg-migrate and if not, you can run ./node_modules/.bin/node-pg-migrate

It will also install pg library as it is peer dependency used for migrations.

Usage

Quick Example

Add "migrate": "node-pg-migrate" to scripts section of package.json so you are able to quickly run commands.

Run npm run migrate create my first migration. It will create file xxx_my-first-migration.js in migrations folder. Open it and change contents to:

exports.up = pgm => {
  pgm.createTable("users", {
    id: "id",
    name: { type: "varchar(1000)", notNull: true },
    createdAt: {
      type: "timestamp",
      notNull: true,
      default: pgm.func("current_timestamp")
    }
  });
  pgm.createTable("posts", {
    id: "id",
    userId: {
      type: "integer",
      notNull: true,
      references: '"users"',
      onDelete: "cascade"
    },
    body: { type: "text", notNull: true },
    createdAt: {
      type: "timestamp",
      notNull: true,
      default: pgm.func("current_timestamp")
    }
  });
  pgm.createIndex("posts", "userId");
};

Save migration file.

Now you should put your DB connection string to DATABASE_URL environment variable and run npm run migrate up. (e.g. DATABASE_URL=postgres://test:test@localhost:5432/test npm run migrate up)

You should now have two tables in your DB 🎉

If you will want to change your schema later, you can e.g. add lead paragraph to posts:

Run npm run migrate create posts lead, edit xxx_posts_lead.js:

exports.up = pgm => {
  pgm.addColumns("posts", {
    lead: { type: "text", notNull: true }
  });
};

Run npm run migrate up and there will be new column in posts table 🎉 🎉

Want to know more? Read docs:

Docs

Explanation & Goals

Why only Postgres? - By writing this migration tool specifically for postgres instead of accommodating many databases, we can actually provide a full featured tool that is much simpler to use and maintain. I was tired of using crippled database tools just in case one day we switch our database.

Async / Sync - Everything is async in node, and that's great, but a migration tool should really just be a fancy wrapper that generates SQL. Most other migration tools force you to bring in control flow libraries or wrap everything in callbacks as soon as you want to do more than a single operation in a migration. Plus by building up a stack of operations, we can automatically infer down migrations (sometimes) to save even more time.

Naming / Raw Sql - Many tools force you to use their constants to do things like specify data types. Again, this tool should be a fancy wrapper that generates SQL, so whenever possible, it should just pass through user values directly to the SQL. The hard part is remembering the syntax of the specific operation, not remembering how to type "timestamp"!

License

The MIT License (MIT)

Copyright (c) 2016-2018 Salsita Software <jando@salsitasoft.com>

Copyright (c) 2014-2016 Theo Ephraim

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

You can’t perform that action at this time.