-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
infoschema: fix error in ParseSlowLog #10526
Conversation
- issue sql: `select * from INFORMATION_SCHEMA.SLOW_QUERY limit 1;` return `ERROR 1105 (HY000): string "2019-05-12-11:23:29.61474688" doesn't has a prefix that matches format "2006-01-02-15:04:05.999999999 -0700", err: parsing time "2019-05-12-11:23:29.61474688" as "2006-01-02-15:04:05.999999999 -0700": cannot parse "" as "-0700"`
Codecov Report
@@ Coverage Diff @@
## master #10526 +/- ##
================================================
+ Coverage 77.2733% 77.3034% +0.0301%
================================================
Files 413 413
Lines 86964 86912 -52
================================================
- Hits 67200 67186 -14
+ Misses 14601 14573 -28
+ Partials 5163 5153 -10 |
@jzdxeb Thanks for contribution. |
bug in version 2.1.8 2.1.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
What problem does this PR solve?
sql:
select * from INFORMATION_SCHEMA.SLOW_QUERY limit 1;
return
ERROR 1105 (HY000): string "2019-05-12-11:23:29.61474688" doesn't has a prefix that matches format "2006-01-02-15:04:05.999999999 -0700", err: parsing time "2019-05-12-11:23:29.61474688" as "2006-01-02-15:04:05.999999999 -0700": cannot parse "" as "-0700"
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes
tidb-ansible
repository