BUG Fix constraints ignoring schema #48
Merged
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
dhensby
added a commit
that referenced
this pull request
Jan 22, 2016
BUG Fix constraints ignoring schema
|
This should be back-ported to 1.2 branch for 3.x compat. |
dhensby
added a commit
to dhensby/silverstripe-postgresql
that referenced
this pull request
Jul 26, 2017
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.
in postgresql, multiple schemas can exist within a single database, so in order to check for constraints (for instance, enum constraint on allowed values) you must always query against the schema.
Some whitespace issues rebasing against the PSR-2 cleaned up version of master, so probably best viewed with ?w=1 on the querystring.
https://github.com/silverstripe/silverstripe-postgresql/pull/48/files?w=1