Question 1

How do I rollback a migration with node-pg-migrate?

Accepted Answer

node-pg-migrate automatically infers down migrations from up operations, so you can run `npm run migrate down` to revert. For custom rollbacks, you may need to define a down function in your migration file, but the tool handles common cases.

Question 2

node-pg-migrate vs knex migrations: which should I use?

Accepted Answer

Choose node-pg-migrate if you're PostgreSQL-focused and prefer raw SQL with automatic down migrations. Knex is more database-agnostic and offers a query builder, but may require more manual work for down migrations and lacks PostgreSQL-specific optimizations.

Question 3

Can I use node-pg-migrate with CockroachDB?

Accepted Answer

Yes, the README states it can work with SQL-standard databases like CockroachDB, though it's built for PostgreSQL. Test with CockroachDB's compatibility, as some PostgreSQL features might not be fully supported.

Question 4

How to run migrations in production with node-pg-migrate?

Accepted Answer

Set the DATABASE_URL environment variable to your production database and run `npm run migrate up` via a script or CI/CD pipeline. Ensure proper error handling and backups, as the tool executes SQL directly.

Question 5

Does node-pg-migrate support data migrations or only schema changes?

Accepted Answer

It primarily focuses on schema changes through its API, but since it allows raw SQL pass-through, you can write data migration scripts directly in SQL within the migration files for flexibility.

Question 6

How to handle multiple database schemas in node-pg-migrate?

Accepted Answer

Check the external documentation for schema management features. The tool likely supports schema operations via its API, but you may need to use raw SQL for complex multi-schema scenarios, as it's PostgreSQL-centric.

node-pg-migrate

What is node-pg-migrate?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions