-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ESCAPE <expression> must not interpret Escape codes. #1638
Comments
It gets stranger by the minute: -- works
select case
when id_portfolio like '%\_1' escape '\\' then '1'
end; This works in JSQLParser but is invalid on oracle: "ORA-01425: escape character must be character string of length 1" |
I understand better, what is going on: the sequence A kind of |
- 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.
* 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
ESCAPE <expression>
must not interpret Escape codes.Odd enough even GitHub Syntax highlighting gets confused?!
The text was updated successfully, but these errors were encountered: