-
-
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
Regression on the parsing of LIKE escape expression in JSQLParser 4.3 #1444
Comments
Greetings, good catch! I will have a look into this tomorrow. |
I think, that has been solved since a while. JSQLParser 4.6 Snapshot parses it just fine: -- Input
select doc.fullName from XWikiDocument doc where doc.fullName like :fullName escape '/' and doc.author like :author escape '!';
-- Output
SELECT doc.fullname
FROM xwikidocument doc
WHERE doc.fullname LIKE :fullName ESCAPE '/'
AND doc.author LIKE :author ESCAPE '!'
; Closed. |
OK, thanks @manticore-projects! I'm looking forward to 4.6 then (I still reproduce with 4.5). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Version 4.3 of JSQLParser seems to introduce a regression in the way LIKE escape expressions are parsed. I assume caused by #420 but did not really look at the code in details.
To Reproduce
Steps to reproduce the behavior:
Given a code which looks like
I end up with
where
being a singleLikeExpression
in which the escape expression includes the whole'/' AND doc.author LIKE :author ESCAPE '!'
part.Expected behavior
In 4.2 the
where
variable is aAndExpression
containing 2LikeExpression
.System
The text was updated successfully, but these errors were encountered: