multi-schema support when parsing/dumping #20
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
peterldowns
force-pushed
the
pd-multi-schema
branch
from
892942b to
4749166
Compare
peterldowns
changed the title
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.
Customers may want to use pgmigrate's parsing/dumping logic with migrations that interact with multiple different Postgres schemas within the same database. Currently, the dumping logic doesn't support this — the code assumes that you're interacting with a single schema, which it assumes by default is named
public. This PR changes that assumption and makes it so that you can parse/dump multiple schemas within the same database.TODO: