-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lexical error from backslash in string literal #1173
Comments
This is connected to quote parsing in JSqlParser. So JSqlParser recognizes \' as an escaped quote and therefore the accepted string literal here is:
which is not your intention. |
I thinking about making this quotation escaping somehow more robust. Probably we should consider making the concrete processing optional. |
manticore-projects
added a commit
to manticore-projects/JSqlParser
that referenced
this issue
Jan 15, 2023
- Enables `\` as escape character in String Literals (beside SQL:2016 compliant `'`) - Default is OFF (since its not SQL:2016 compliant) - Activate per Parser Feature - Fixes JSQLParser#1638 - Fixes JSQLParser#1209 - Fixes JSQLParser#1173 - Fixes JSQLParser#1172 - Fixes JSQLParser#832 - Fixes JSQLParser#827 - Fixes JSQLParser#578 BREAKING-CHANGE: Backslash Escaping needs to be activated explicitly or else Backslash won't work as Escape Character.
Merged
wumpz
pushed a commit
that referenced
this issue
Jan 20, 2023
* refactor: Merge REPLACE into UPSERT fixes #1706 * feat: `DROP TEMPORARY TABLE ...` fixes #1712 * build: PMD compliance * ci: Merge master * feat: Configurable backslash `\` escaping - Enables `\` as escape character in String Literals (beside SQL:2016 compliant `'`) - Default is OFF (since its not SQL:2016 compliant) - Activate per Parser Feature - Fixes #1638 - Fixes #1209 - Fixes #1173 - Fixes #1172 - Fixes #832 - Fixes #827 - Fixes #578 BREAKING-CHANGE: Backslash Escaping needs to be activated explicitly or else Backslash won't work as Escape Character. * style: Checkstyle * style: remove dead code * style: PMD compliance * style: Checkstyle, unused import * feat: allow `S_CHAR_LITERAL` to break lines - fixes #875
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Lexical error for Oracle update statement when where clause has backslash in string literal.
To Reproduce
Steps to reproduce the behavior:
System
The text was updated successfully, but these errors were encountered: