postgrator - npm Package Versions

8.0.0

November 11, 2024

• Update glob to latest dependency, which technically only supports Node v20 or later. Which technically, makes this a breaking change?

7.3.0

September 3, 2024

• Support sqlite3 and better-sqlite3 migrations with ; in statements.

• Add execSqlScript option to execute migrations consisting of multiple statements. If not supplied, Postgrator will fallback to using execQuery.

7.2.0

July 9, 2023

• Support better-sqlite3

7.1.1

September 21, 2022

• Fix migration method code comment
• Use INTEGER for sqlite3 version type

7.1.0

March 31, 2022

• Add sqlite3 support

7.0.0

February 23, 2022

• getDatabaseVersion returns 0 when schema version table does not exist instead of undefined. This is technically breaking if you rely on the undefined returned in version 5.0.1.
• Fix DEP0151 warning about ext resolution

6.0.0

February 21, 2022

Breaking

Postgrator is now an ES module and requires Node 14 or later. .cjs and .mjs migration files are now supported.

No other changes have been made.

5.0.1

February 18, 2022

• Fix getDatabaseVersion error when schemaversion table does not exist. undefined is returned instead.

5.0.0

October 14, 2021

Version 5 represents an effort to simplify things, allow more flexibility, and reduce the maintenance of this package.

This is made possible by requiring the database query execution function be injected to postgrator. Postgrator no longer manages the database connection, and as a result no longer needs to maintain a mapping to specific database driver implementations.

Despite all the breaking changes below, nothing has changed in the overall migration file approach. Migrations that worked for previous versions of postgrator will still work in v5.

See examples/ directory for quick overview of how v5 is used.

Features

• md5 validation may be skipped for specific migrations by deleting the md5 value from your DB's schemaversion table.

Fixes

• Honors uppercase characters in postgres schema table name (#98)
• JS migrations no longer run during validation, preventing unwanted migration failures (#124)

BREAKING

• Nodejs 12 or later required.
• Removed host, port, username, password, ssl, options. Manage connections with execQuery instead.
• Driver value mysql2 unsupported. (You can still use the mysql2 package for your execQuery implementation, but set driver to mysql)
• RemovedmigrationDirectory option. Use migrationPattern instead. In most cases it will be path/to/migrations/*. Any glob syntax supported.
• Removed GO keyword splitting for mssql. Using GO could leave your system in a partially migrated state on failure and is not recommended.
• filename in migration result is full file path
• Removed md5 checksum validation for JS migrations. JS migrations are dynamic, and JS style trends could vary over time if a tool like Prettier is applied.
• JS migrations do not generate SQL until immediately prior to being applied. Previously, JS migrations generated SQL prior to any migrations running. This was problematic for cases where JS migrations no longer successfullly generated SQL.

4.3.1

October 9, 2021

• Undeprecate currentSchema config. It'll stay for v5.