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: parse datatime won't truncate the reluctant string #22231

Closed
AilinKid opened this issue Jan 6, 2021 · 3 comments · Fixed by #22232
Closed

time: parse datatime won't truncate the reluctant string #22231

AilinKid opened this issue Jan 6, 2021 · 3 comments · Fixed by #22232
Assignees
Labels
severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@AilinKid
Copy link
Contributor

AilinKid commented Jan 6, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

select cast('2020-05-28 23:59:59 00:00:00' as datetime);

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

+--------------------------------------------------+
| cast('2020-05-28 23:59:59 00:00:00' as datetime) |
+--------------------------------------------------+
| 2020-05-28 23:59:59                              |
+--------------------------------------------------+
1 row in set, 1 warning (0.01 sec)

3. What did you see instead (Required)

+--------------------------------------------------+
| cast('2020-05-28 23:59:59 00:00:00' as datetime) |
+--------------------------------------------------+
| NULL                                             |
+--------------------------------------------------+
1 row in set, 1 warning (0.00 sec)

4. What is your TiDB version? (Required)

current master 8ef1031

@tangenta
Copy link
Contributor

tangenta commented Jan 6, 2021

Why is it a critical bug? 😕

@aytrack
Copy link
Contributor

aytrack commented Jan 6, 2021

Because "Bugs caused by type casts" are critical bugs. So I change the label to critical.

@ti-srebot
Copy link
Contributor

ti-srebot commented Jan 7, 2021

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

[v3.0.0:v3.0.20],[v4.0.0:v4.0.10][v5.0.0-rc]

6. Fixed versions

master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major 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.

5 participants