-
Notifications
You must be signed in to change notification settings - Fork 978
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
Better parsing of USE queries sent with COM_QUERY #4598 #4605
Conversation
Some of the test in List of all tests: https://github.com/sysown/proxysql/blob/v2.6.3/test/tap/tests/reg_test_3493-USE_with_comment-t.cpp#L171-L185
|
retest this please |
This seems to have introduced problem with laravel's doctrine: [2024-08-29 08:52:28] developmnet.ERROR: SQLSTATE[42000]: Syntax error or access violation: 1148 Unable to parse: use Reverting proxysql to 2.6.3 solved our problem. Laravel config:
|
@TomaszKorwel , yes, we are aware.
On our end, we missed removing the semicolon from queries sent by application like Laraval . |
Thanks! |
Closes #4598
USE
queries sent viaCOM_QUERY
are not processed in a better way, improving their parsing:SetParser
(even if it is not aSET
statement !! , to minimize code changes)USE
and dbname is optionalThis new parser passes the tests in existing
reg_test_3493-USE_with_comment-t
TAP test, and it also introduced a new set of tests that are automatically executed in debug build.