Open
Conversation
As of PostgreSQL 9.1 the configuration parameter standard_conforming_strings is on by default. This means that it is required to specify letter E before the string if you want to use C-style escapes. See more here: https://www.postgresql.org/docs/9.2/static/sql-syntax-lexical.html
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As of PostgreSQL 9.1 the configuration parameter
standard_conforming_strings is on by default.
This means that it is required to specify letter E before the string
if you want to use C-style escapes.
See more here:
https://www.postgresql.org/docs/9.2/static/sql-syntax-lexical.html
P.S. I'm not sure if it brakes the support of other RDBMS but I'm making a PR anyway
to see if it makes sense as a generic solution.