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

"Invalid time format" caused by time zone issue #13605

Closed
shenli opened this issue Nov 20, 2019 · 1 comment · Fixed by #13614
Closed

"Invalid time format" caused by time zone issue #13605

shenli opened this issue Nov 20, 2019 · 1 comment · Fixed by #13614
Assignees
Labels
type/bug The issue is confirmed as a bug.

Comments

@shenli
Copy link
Member

shenli commented Nov 20, 2019

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.
    I am in the -8:00 time zone.
➜  work date -R
Tue, 19 Nov 2019 15:51:45 -0800

With the following operation, I meet the invalid time format issue.

use test;
set @@time_zone = '+0:00';
SELECT @@global.time_zone, @@session.time_zone;
create table t (ts timestamp);
insert into t values ("2018-03-11 02:00:16");
  1. What did you expect to see?
Query OK, 1 row affected (0.01 sec)
  1. What did you see instead?
ERROR 1292 (22007): invalid time format: '{2018 3 11 2 0 16 0}'
  1. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?
| Release Version: v4.0.0-alpha-921-g77faf6466-dirty
Git Commit Hash: 77faf64668213114ea33f565c84dde52a5359667
Git Branch: master
UTC Build Time: 2019-11-19 11:23:59
GoVersion: go version go1.13.4 darwin/amd64
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
@shenli shenli added the type/bug The issue is confirmed as a bug. label Nov 20, 2019
@bb7133 bb7133 self-assigned this Nov 20, 2019
@bb7133
Copy link
Member

bb7133 commented Nov 20, 2019

This bug is related to the Daylight Saving Times and we will fix it soon.

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

Successfully merging a pull request may close this issue.

3 participants