Run migration tests in a non-public schema as part of CI
#279
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
exekias
approved these changes
Feb 6, 2024
b3d115c to
35c3a2e
Compare
Run the tests twice for each pg version; once applying migrations in the `public` schema and once in the `non_public` schema.
Run the examples twice for each pg version; once applying migrations in the `public` schema and once in the `non_public` schema.
Don't cancel other jobs in the matrix when one fails.
35c3a2e to
361a274
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add another dimension to the test matrix so that migration tests are run in both the
publicand a non-publicschema.#276 made it possible to run migration tests in schema other than
public. Doing so highlighted some issues that are fixed by #278.Fixes #273.