[MDEV-28047] MariaDB don't accept timestamp in range 2022-03-13 02:00:00.000 - 2022-03-13 03:00:00.000 Created: 2022-03-12  Updated: 2022-03-12  Resolved: 2022-03-12

Status: Closed
Project: MariaDB Server
Component/s: Data Manipulation - Insert
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Yevhen Chypachenko Assignee: Sergei Golubchik
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-28046 MariaDB don't accept timestamp in ran... Closed

 Description   

MariaDB Version: 10.2.31-MariaDB-log
ENV Timezone: EST

MariaDB server don't accept timestamp values in range 2022-03-13 02:00:00.000 - 2022-03-13 03:00:00.000 (GMT) (12th March 9PM - 10PM EST)
UNIX time in mills is from 1647136800 to 1647140400
Probably it's related to Daylight Saving Time change

STR

CREATE TABLE my_table (
	id INT auto_increment NOT NULL,
	created TIMESTAMP NULL,
	CONSTRAINT my_table_pk PRIMARY KEY (id)
)
ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;
 
 
INSERT INTO my_table (created) VALUES('2022-03-13 01:59:00');
-- inserted
 
INSERT INTO my_table (created) VALUES('2022-03-13 02:00:00');
SQL Error [1292] [22007]: (conn=102) Incorrect datetime value: '2022-03-13 02:00:00' for column `equity_970_ctg`.`my_table`.`created` at row 1
 
 
INSERT INTO my_table (created) VALUES('2022-03-13 02:59:59');
SQL Error [1292] [22007]: (conn=102) Incorrect datetime value: '2022-03-13 02:59:59' for column `equity_970_ctg`.`my_table`.`created` at row 1
 
 
INSERT INTO my_table (created) VALUES('2022-03-13 03:00:00');
-- inserted

It is a critical issue for us, and tomorrow all systems will be broken for 1 hour.
Please provide any workaround ASAP


Generated at Thu Feb 08 09:57:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.