Skip to content
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

time type in in function will get wrong result #21290

Closed
xiongjiwei opened this issue Nov 25, 2020 · 3 comments · Fixed by #21293
Closed

time type in in function will get wrong result #21290

xiongjiwei opened this issue Nov 25, 2020 · 3 comments · Fixed by #21293
Labels
severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Milestone

Comments

@xiongjiwei
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table t1(a date);
insert into t1 values (20100202);
select a in ('2020-02-02', '2010-02-02') from t1;

2. What did you expect to see? (Required)

1

3. What did you see instead (Required)

0

4. What is your TiDB version? (Required)

@xiongjiwei
Copy link
Contributor Author

@TennyZhuang hi, PTAL The Time type has compare function, is it same with ==? also, it has getCoreTime function. What the difference among A==B, A.compare(B) and A.getCoreTime==B.getCoreTime?

@jebter jebter added this to the v4.0.10 milestone Nov 27, 2020
@jebter jebter added the sig/execution SIG execution label Nov 27, 2020
@xiongjiwei
Copy link
Contributor Author

CoreTime.compare function use first 60bit to compare time, which is same with uint64(a)&coreTimeBitFieldMask

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants