-
Notifications
You must be signed in to change notification settings - Fork 981
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
Add support for 'grave accent' (`) for SET statements parsing #3479
Comments
JavierJF
added a commit
that referenced
this issue
Jun 12, 2021
…tements' for tracked variables #3479
JavierJF
added a commit
that referenced
this issue
Jun 12, 2021
… regex matching variable name #3479
JavierJF
added a commit
that referenced
this issue
Jun 12, 2021
…' and 'test_filtered_set_statements-t' #3479
renecannao
added a commit
that referenced
this issue
Jun 28, 2021
Closes #3479: Add support for 'grave accent' (`) for SET statements parsing
JavierJF
added a commit
that referenced
this issue
Aug 31, 2021
…tements' for tracked variables #3479
JavierJF
added a commit
that referenced
this issue
Aug 31, 2021
… regex matching variable name #3479
JavierJF
added a commit
that referenced
this issue
Aug 31, 2021
…' and 'test_filtered_set_statements-t' #3479
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now whenever a SET statement is issued containing grave accents like for example:
ProxySQL will fail to parse the query resulting into a message like:
And locking the hostgroup because of it.
v2.2.0
Issue any set statements in which the variable is surrounded by grave accents. Another example:
Results in:
The text was updated successfully, but these errors were encountered: