PostgresDB Versioning

Relational databases must be versioned if their data and tables are to be migrated properly over time. This project seeks to produce an NPM module which does the heavy lifting using configuration and version data supplied by whatever depends on this module.

Configuration

{
"connectionConfig": {
"user": "postgres",
"password": "postgres",
"host": "localhost",
"database": "postgres",
"port": 54231
},
"dryRun": false
"eventHandler": (...eventArgs) => console.error(event),
"migrations": [
{"version": 1, "description": "create the table a_table", "sql": "CREATE TABLE a_table (id INT);"},
{"version": 2, "description": "add the table another_table", "sql": "CREATE TABLE another_table (id INT);"}
],
"pool": {
query: sqlString => console.error(sqlString)
},
"requestedVersion": 2,
"scratch": [
"CREATE TABLE table_name"
],
"tableNameForVersions": "DatabaseVersion",
"version": 1
}

$3

If this module should manage the connection, then pass in a config object with this API: https://node-postgres.com/api/client/.

$3

With this feature enabled, the steps which would be performed will be sent as events to the event handler.

$3

If this is set, it will emit events (either a string for the query or an array crafted from the (...args) which will be applied to the query function call.

For example, if the eventHandler is called with multiple arguments, such as: 'SELECT * FROM x WHERE x.y = ?;' and ['fred'], then when the plan executes, it would execute something like this:

pool.query('SELECT * FROM x WHERE x.y = ?;', ['fred']);

If the eventHandler is called with just a string, like 'SELECT * FROM x;', it would execute something like this:

pool.query('SELECT * FROM x');

$3

Migrations should be an array of objects containing a version number, an optional description of the changes, and the sql that should be executed.

$3

If included, this will be used blindly to send queries to the DB. It will be assumed that it implements this API: https://node-postgres.com/api/pool/. This option takes priority over "connectionConfig", so don't provide "pool" if you want to use "connectionConfig".

$3

If provided, it will stop trying to migrate at the requested version. This will disable use of scratch if the "version" is greater than the "options"."requestedVersion".

If not provided, the max of "options"."version" and of the highest "version" in "options"."migrations" will be used.

$3

If provided, the scratch array will be used to populate the database if the "tableNameForVersions" table is not yet present. Migrations with a "version" greater than "options"."version" will be also executed by making the assumption that the "options"."version" version has been achieved.

If not provided, the migrations array will be used.

$3

This allows you change the name used to track versions of the DB.

$3

This should be the same as the version which is created by "scratch".