[MCOL-265] TIMESTAMP data type not supported Created: 2016-08-18  Updated: 2022-01-05  Resolved: 2019-09-11

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.0

Type: New Feature Priority: Minor
Reporter: Andrew Hutchings (Inactive) Assignee: Bharath Bokka (Inactive)
Resolution: Fixed Votes: 6
Labels: contribution, documentation, relnote

Issue Links:
Relates
relates to MCOL-1039 DATE / DATETIME should support CURREN... Closed
relates to MCOL-4957 Functions on TIMESTAMP columns in pro... Closed
relates to MCOL-3694 TIMESTAMP data type is accepted but c... Closed
Epic Link: ColumnStore Compatibility Improvements
Sprint: 2019-04, 2019-05, 2019-06

 Description   

DATETIME data type appears to work whereas any CREATE TABLE with a TIMESTAMP type throws an error

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-04-25 ]

External contribution, Roman to final review

Comment by Andrew Hutchings (Inactive) [ 2019-05-02 ]

Contribution may need some changes. TBD.

Comment by Bharath Bokka (Inactive) [ 2019-09-11 ]

TIMESTAMP data type works as expected in 1.4.0-1.

Build-
server commit:
67452bc
engine commit:
4d2a159

Ex:
MariaDB [test]> create table t3(col1 timestamp) engine=columnstore;
Query OK, 0 rows affected (0.548 sec)

MariaDB [test]>
MariaDB [test]> show create table t3;
------------------------------------------------------------------------------------------------------------------------------------------------------------+

Table Create Table

------------------------------------------------------------------------------------------------------------------------------------------------------------+

t3 CREATE TABLE `t3` (
`col1` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()
) ENGINE=Columnstore DEFAULT CHARSET=latin1

------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.001 sec)

MariaDB [test]> insert into t3 values();
Query OK, 1 row affected (0.215 sec)

MariaDB [test]>
MariaDB [test]> insert into t3 values('2038-01-19 03:14:08');
Query OK, 1 row affected, 1 warning (0.143 sec)

MariaDB [test]> insert into t3 values('2038-01-19 03:14:07');
Query OK, 1 row affected (0.114 sec)

MariaDB [test]> insert into t3 values('1970-01-01 00:00:01');
Query OK, 1 row affected (0.135 sec)

MariaDB [test]> insert into t3 values('1970-01-01 00:00:00');
Query OK, 1 row affected, 1 warning (0.106 sec)

MariaDB [test]> insert into t3 values(now());
Query OK, 1 row affected (0.158 sec)

MariaDB [test]> insert into t3 values(current_timestamp());
Query OK, 1 row affected (0.184 sec)

MariaDB [test]> select * from t3;
---------------------

col1

---------------------

2019-09-09 10:57:02
0000-00-00 00:00:00
2038-01-19 03:14:07
1970-01-01 00:00:01
0000-00-00 00:00:00
2019-09-09 11:11:47
2019-09-09 11:12:02

---------------------
7 rows in set (0.104 sec)

MariaDB [test]> select * from t3 where col1 > '2019-09-09 10:57:02';
---------------------

col1

---------------------

2038-01-19 03:14:07
2019-09-09 11:11:47
2019-09-09 11:12:02

---------------------
3 rows in set (0.013 sec)

MariaDB [test]> select * from t3 where col1 < '2019-09-09 10:57:02';
---------------------

col1

---------------------

0000-00-00 00:00:00
1970-01-01 00:00:01
0000-00-00 00:00:00

---------------------

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