rickbergfalk / postgrator

A PostgreSQL, MySQL, and SQL Server migration tool using plain sql scripts.

rickbergfalk/postgrator Issues

Cannot run skipped migration without rolling back
Updated 7 months ago1
Connecting to Postgres on Ubuntu using connectionString
Updated 2 years ago
Cannot pass number as version to migrate
Updated 2 years ago
How to use different schemas with Postgres?
Updated 2 years ago1
Removing broken migrations
Updated 2 years ago1
Migration fails with node-postgres' default connection configuration
Updated 2 years ago1
SQLite support
Closed 2 years ago1
Error when trying to get the current DB version
Closed 2 years ago7
Deprecation warning reported for v6.0.0
Closed 2 years ago1
Support *.cjs files in migration directory
Closed 2 years ago5
Js migrations can throw errors when not run
Closed 3 years ago5
Using upper case characters in schemaTable with postgresql lead to an error
Closed 3 years ago1
It's not clear how "undo" files are suposed to be used
Closed 3 years ago2
How to fix/proceed after an md5 conflict has been detected?
Closed 3 years ago3
TypeError: postgrator.setConfig is not a function
Closed 3 years ago3
Option to skip MD5 hashing
Closed 3 years ago6
mssql tedious warning `enableArithAbort`
Closed 3 years ago1
Errors generated by getDatabaseVersion() before migrate() won't close DB connection
Closed 3 years ago1
Postgrator not handling multi-line comments correctly
Closed 3 years ago7
Usage with existing database
Closed 3 years ago2
Migrations may be run twice
Closed 3 years ago1
Retrieve postgresql messages / logging
Closed 3 years ago2
Support for socketPath option for mysql driver
Closed 3 years ago2
Support injecting the db connection
Closed 3 years ago5
Please add support for node-mssql version 7.x
Closed 3 years ago2
(Postgresql) Upper Case Table and Schema name.
Closed 4 years ago
Proposal: Promises support for javascript migrations
Closed 4 years ago5
MD5 checksum error for migration that is not in schemaversion
Closed 4 years ago3
(Postgresql) Migration applied if the update of the schemaversion table throws an error
Updated 4 years ago1
schemaversions version field cannot hold values larger than maxint
Closed 4 years ago1
has an issue with non default schema for mssql
Closed 5 years ago2
Support for node-mssql version 6.0.0
Closed 5 years ago1
Insert / pre-populate migrations schema to reflect migrations manually applied before Postgrator first use
Updated 5 years ago5
Support mssql version 5
Closed 5 years ago1
Support for include path statement
Closed 5 years ago2
Postgrator not detecting changes to sql files
Closed 5 years ago1
Suggestion: Allow connection strings.
Closed 5 years ago1
QUESTION: how do I programatically rollback?
Closed 6 years ago1
Managed PG on Azure
Closed 6 years ago6
Postgrator tries to create a version table every startup even when already exists
Closed 6 years ago2
Script never ends on error during migration.
Closed 6 years ago1
Slow query
Closed 6 years ago2
Organize migrations into subdirectories?
Closed 6 years ago3
Support for DATABASE_URL environment variable
Closed 6 years ago1
Postgrator fails when database has already schemaversion table with different schema, mssql
Closed 6 years ago1
Thank you Rick!
Closed 6 years ago1
Check for table_schema in commonClient.ensureTable
Closed 6 years ago2
Cannot connect to Postgres
Closed 6 years ago14
Can we expose getMigrations()?
Closed 7 years ago5
Use promises instead of functions?
Closed 7 years ago1