We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a query selects VitessAware system variables, without passing the query down to MySQL. A value of type NULL is returned.
This issue applies to boolean-typed variables.
Whenever the query implies being sent down to MySQL, the variable's value is correctly returned.
Steps to reproduce this issue:
mysql> set @@autocommit = 1; Query OK, 0 rows affected (0.00 sec)
Can also be set with on.
on
mysql> select @@autocommit; +--------------+ | @@autocommit | +--------------+ | NULL | +--------------+ 1 row in set (0.01 sec)
mysql> select @@autocommit from corder; +--------------+ | @@autocommit | +--------------+ | 1 | | 1 | | 1 | | 1 | | 1 | +--------------+ 5 rows in set (0.00 sec)
Version: 36110d81b (Git branch 'master') built on Fri Jan 15 16:45:21 CET 2021 by [email protected] using go1.15.5 darwin/amd64
Ran on the 101 local example.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Overview of the Issue
When a query selects VitessAware system variables, without passing the query down to MySQL. A value of type NULL is returned.
This issue applies to boolean-typed variables.
Whenever the query implies being sent down to MySQL, the variable's value is correctly returned.
Reproduction Steps
Steps to reproduce this issue:
Binary version
Operating system and Environment details
Ran on the 101 local example.
The text was updated successfully, but these errors were encountered: