Repository navigation
ESCAPE <expression> must not interpret Escape codes. #1638
Description
ESCAPE <expression> must not interpret Escape codes.
-- fails
select case
when id_portfolio like '%\_1' escape '\' then '1'
end;
-- works
select case
when id_portfolio like '%\_1' then '1'
end;
-- works
select *
from dual
where id_portfolio like '%\_1' escape '\';Odd enough even GitHub Syntax highlighting gets confused?!
Activity
manticore-projects commentedon Sep 24, 2022
It gets stranger by the minute:
This works in JSQLParser but is invalid on oracle: "ORA-01425: escape character must be character string of length 1"
manticore-projects commentedon Oct 14, 2022
I understand better, what is going on: the sequence
ESCAPE '\'collides with the<ESC> tokendefined in the Grammar.In the result, the Escape Expression becomes
<S_CHARLITERAL> = '\' then '1'(including the<ESC>Token).A kind of
UNESCAPED CHAR LITERALwill also not work because the LONGEST MATCH is chosen over the shortest match.[-]CASE WHEN has problem with LIKE ESCAPE[/-][+]ESCAPE <expression> must not interpret Escape codes.[/+]feat: Configurable backslash `\` escaping
Assorted Fixes #5 (#1715)