fixes for constraint name handling when creating keys and foreign keys #257
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
- refactor common code for generating default names - always return proper schema string in responses, ignoring input placeholders - fix longstanding bugs in pseudo-constraint creation handlers the pseudo constraint fixes are only relevant for rare catalogs that have locally provisioned SQL views, and then the rest API is used to add pseudo key or foreign key constraints related to these views.
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.
the pseudo constraint fixes are only relevant for rare catalogs that have locally provisioned SQL views, and then the rest API is used to add pseudo key or foreign key constraints related to these views.