DM-36497: Add support for specifying schema name for tables #28
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
ebellm
approved these changes
Oct 7, 2022
Adds a configuration field to ApdbSqlConfig which can specify alternative schema name to use for all tables. Schema needs to be created in advance, by default the default schema is used. Also adds a separate unit test case for Postgres (only runs if testing.postgres exists), which tests non-default schema name.
andy-slac
force-pushed
the
tickets/DM-36497
branch
from
ecacdb9
to
bbf288c
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.
Adds a configuration field to ApdbSqlConfig which can specify alternative schema name to use for all tables. Schema needs to be created in advance, by default the default schema is used. Also adds a separate unit test case for Postgres (only runs if testing.postgres exists), which tests non-default schema name.