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
Incorrect result
Frontend
Cannot set timezone in mysql any more
MySQL [public]> SET time_zone = 'UTC'; Query OK, 0 rows affected (0.001 sec) MySQL [public]> SELECT @@time_zone; +-------------+ | @@time_zone | +-------------+ | | +-------------+ 1 row in set (0.000 sec) MySQL [public]> SET time_zone = '+08:00'; Query OK, 0 rows affected (0.000 sec) MySQL [public]> SELECT @@time_zone; +-------------+ | @@time_zone | +-------------+ | | +-------------+ 1 row in set (0.000 sec) MySQL [public]> SET time_zone = 'Europe/Berlin'; Query OK, 0 rows affected (0.000 sec) MySQL [public]> SELECT @@time_zone; +-------------+ | @@time_zone | +-------------+ | | +-------------+ 1 row in set (0.000 sec)
any
No response
Open a mysql client console and follow docs: https://docs.greptime.com/user-guide/protocols/mysql#time-zone
Execute SELECT @@time_zone returns empty result
SELECT @@time_zone
The text was updated successfully, but these errors were encountered:
Broken by e0aecc9
Always new a QueryContext for every request. Must use session.context() instead.
QueryContext
session.context()
Sorry, something went wrong.
sunng87
Successfully merging a pull request may close this issue.
What type of bug is this?
Incorrect result
What subsystems are affected?
Frontend
What happened?
Cannot set timezone in mysql any more
What operating system did you use?
any
Relevant log output and stack trace
No response
How can we reproduce the bug?
Open a mysql client console and follow docs: https://docs.greptime.com/user-guide/protocols/mysql#time-zone
Execute
SELECT @@time_zone
returns empty resultThe text was updated successfully, but these errors were encountered: