Skip to content

Separate MySQL Special String Functions colliding with InExpression #1285

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

Conversation

manticore-projects
Copy link
Contributor

Separate MySQL Special String Functions accepting Named Argument Separation as this could collide with ComplexExpressionList when InExpression is involved

-- this is a ComplexExpressionList which must NOT be parsed as NamedParameterList
SELECT test('foo' in ('bar') and 1=1); 

-- this is a NamedParameterList but only for a few Special String Functions
SELECT substring('foo' in 'bar'); 

Fixes #1284

…ration as this could collide with ComplexExpressionList when InExpression is involved

Fixes JSQLParser#1284
@coveralls
Copy link

Coverage Status

Coverage increased (+0.003%) to 88.688% when pulling 1427b65 on manticore-projects:SpecialStringFunctionWithNamedParameters into f85b4b6 on JSQLParser:master.

@wumpz wumpz merged commit c074a21 into JSQLParser:master Jul 26, 2021
@manticore-projects manticore-projects deleted the SpecialStringFunctionWithNamedParameters branch May 31, 2022 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IF(boolean, 0, 1) Function parse ERROR
3 participants