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
Standalone mode
First create table and insert data:
mysql> create table test(ts timestamp time index, a int); Query OK, 0 rows affected (30.06 sec) mysql> insert into test values(1,1); Query OK, 1 row affected (0.03 sec) mysql> select * from test; +----------------------------+------+ | ts | a | +----------------------------+------+ | 1970-01-01 00:00:00.001000 | 1 | +----------------------------+------+ 1 row in set (0.07 sec)
Then select * from test where ts = '1970-01-01 00:00:00.001000';.
select * from test where ts = '1970-01-01 00:00:00.001000';
The result is empty, which is incorrect.
Two walkaround:
select * from test where ts = “1970-01-01 00:00:00.001000”::timestamp_ms;
select * from test where ts = "1970-01-01 08:00:00.001000"
select non-empty data
select empty data
all
No response
The text was updated successfully, but these errors were encountered:
@waynexia What's the status of this issue?
Sorry, something went wrong.
It's fixed in #2905
waynexia
Successfully merging a pull request may close this issue.
What type of bug is this?
Incorrect result
What subsystems are affected?
Standalone mode
Minimal reproduce step
First create table and insert data:
Then
select * from test where ts = '1970-01-01 00:00:00.001000';
.The result is empty, which is incorrect.
Two walkaround:
select * from test where ts = “1970-01-01 00:00:00.001000”::timestamp_ms;
select * from test where ts = "1970-01-01 08:00:00.001000"
What did you expect to see?
select non-empty data
What did you see instead?
select empty data
What operating system did you use?
all
Relevant log output and stack trace
No response
The text was updated successfully, but these errors were encountered: