[MDEV-13062] Timestamp & '2017-03-12T02:40:50.596675' Created: 2017-06-12  Updated: 2017-06-13  Resolved: 2017-06-13

Status: Closed
Project: MariaDB Server
Component/s: Time zones
Affects Version/s: 10.2.6
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Lawrence Dumaguing Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: timestamp
Environment:

Red Hat Linux 7.3


 Description    

drop table if exists AAAAA;
 
create table AAAAA (
 
   ID INT NOT NULL PRIMARY KEY,
 
   FULLNAME VARCHAR(125),
 
   TS TIMESTAMP
 
) ENGINE=InnoDB CHARACTER SET latin1;
 
 
 
 
 
insert into AAAAA values (1, 'Moe',   '2017-03-11T02:40:50.596675');
 
insert into AAAAA values (2, 'Curly', '2017-03-12T02:40:50.596675');  <------ unable to insert this datum
 
insert into AAAAA values (3, 'Larry', '2017-03-13T02:40:50.596675');​



 Comments   
Comment by Sergei Golubchik [ 2017-06-13 ]

This is not a bug.

Indeed timestamp 2017-03-12 02:40:50.596675 is invalid, there was never a point in time where your clock have shown it — after 2017-03-12 01:59 they were showing 2017-03-12 03:00. That was when your time zone have switched to DST.

Generated at Thu Feb 08 08:02:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.