[MCOL-4514] DATE + INTERVAL a SECOND is not like in MariaDB Created: 2021-01-22  Updated: 2023-07-02

Status: Open
Project: MariaDB ColumnStore
Component/s: PrimProc
Affects Version/s: 5.4.3, 6.1.1
Fix Version/s: Icebox

Type: Bug Priority: Minor
Reporter: Alexander Barkov Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MCOL-4416 FROM_UNIXTIME() returns a bad result ... Open
relates to MCOL-4418 SEC_TO_TIME() returns a wrong result ... Open
relates to MCOL-4419 MAKETIME() returns a wrong result for... Open
relates to MCOL-4420 DATE_ADD() returns a wrong result for... Open

 Description   

This is similar to MCOL-4420, however for VARCHAR input instead of DECIMAL input.

DROP TABLE IF EXISTS t1;
 
CREATE TABLE t1 (a VARCHAR(10)) ENGINE=MyISAM;
 
INSERT INTO t1 VALUES ('1.9');
 
SELECT TIMESTAMP'2001-01-01 00:00:00' +  INTERVAL a SECOND FROM t1;


+-----------------------------------------------------+
 
| TIMESTAMP'2001-01-01 00:00:00' +  INTERVAL a SECOND |
 
+-----------------------------------------------------+
 
| 2001-01-01 00:00:01.900000                          |
 
+-----------------------------------------------------+


DROP TABLE IF EXISTS t1;
 
CREATE TABLE t1 (a VARCHAR(10)) ENGINE=COLUMNSTORE;
 
INSERT INTO t1 VALUES ('1.9');
 
SELECT TIMESTAMP'2001-01-01 00:00:00' +  INTERVAL a SECOND FROM t1;


+-----------------------------------------------------+
 
| TIMESTAMP'2001-01-01 00:00:00' +  INTERVAL a SECOND |
 
+-----------------------------------------------------+
 
| 2001-01-01 00:00:01.000000                          |
 
+-----------------------------------------------------+

Notice, unlike MyISAM, with ColumnStore the fractional part is set to zeros instead of '.900000'.
Generated at Thu Feb 08 02:50:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.