postgres-migrations

postgres-migrations copied to clipboard

add dryRun to migrate

9

PR for #89 Also tested it manually against a codebase on my machine.

MatthewBurstein

schema of migrations table

5

Is it possible to specify the schema of the migrations table? I'd like to separate tables by schema, and have separate migrations for each schema. That way, I can do...

dlidstrom

Check table exists in current search path

2

This PR adds tests to PR #33 which will ultimately fix a bug where schemas are ignored when checking for the presence of a migrations table. Note: the tests do...

slifty

Make `doesTableExist` check for table in current search path

6

* If a `migrations` table did exist in a schema outside of the search path, `doesTableExist` would return true but the migration would then fail with 'relation "migrations" does not...

remiremi

Migrations can't be run on multiple schemas in the same database

2

I am using schemas to parallelize integration tests (one schema per test worker). Before each test I want to run the following setup: 1. Create a new schema 2. Set...

slifty

Feature request: dry run functionality

2

For my CI pipeline, I would like to be able to dry run migrations so that I can show what migrations will run, then request approval from the user, then...

MatthewBurstein

doesn't work when bundled

12

Because of this line the sql file ends up checking the relative location in this case it's `dist` instead of `node_modules`. Maybe inline this so it can be bundled? Or...

OmgImAlexis

To avoid problems with esnext

saintedlama

rename cause to reason to avoid esnext conflicts

3

saintedlama

MigrateDBConfig does not support pre-existing client and ensureDatabaseExists at the same time

4

I noticed the `createDb` was marked as deprecated, so I moved to refactor my code to support the newer syntax. In my client I'd like to do the following: ```ts...

Tethik