Slash before '_' in postgresql like condition with 'pg_' prefix to prevent confusion with the wildcard character #2670
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
|
@blackbjorn thx! |
|
Backported to |
blackbjorn
deleted the
postgresql-slash-before-underscore-in-like-condition
branch
Ocramius
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There are conditions
schema not like 'pg_%'for exclude system tables, sequence etc. (system prefixpg_) in some queries for postgresql platform.But in like condition symbol
_means "any single character" (docs)It's the cause of problems when schema name starts with
pg<non underscore character>(pgpfor example), but it's valid schema name.