Fix previous_version function to work with non-public schema
#190
Conversation
This file contains 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
Extend the test case that checks that the 'schema' option is respected; run another migration after the first. Assert that the version schema for the first migration is dropped on completion of the second.
To get rid of the hard-coded `'public'` schema name.
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.
Fix the
previous_versionfunction so that it works correctly for migrations applied in schema other thanpublic.In particular, this meant that the previous version schema would not be removed on migration completion for migrations applied in schema other than
public.Extend the test that checks the
--schemaflag is respected with the extra coverage that would have caught this.