Recent test depends from local host timezone and fails if it is not UTC

[klirichek]

Recent test depends from local host timezone and fails if it is not UTC

[sanikolaev]

Looks like it considers the entered time is in UTC instead of converting it to UTC internally from the current time zone.

MRE:

mysql> set global timezone='Asia/Novosibirsk'; drop table if exists rt1; create table rt1(tid timestamp); INSERT into rt1 (id, tid) values (3, '2022-01-01T00:00'); SELECT id, date_format(tid, '%Y-%m-%dT%H:%M') from rt1;
--------------
set global timezone='Asia/Novosibirsk'
--------------

Query OK, 0 rows affected (0.00 sec)

--------------
drop table if exists rt1
--------------

Query OK, 0 rows affected (0.08 sec)

--------------
create table rt1(tid timestamp)
--------------

Query OK, 0 rows affected (0.00 sec)

--------------
INSERT into rt1 (id, tid) values (3, '2022-01-01T00:00')
--------------

Query OK, 1 row affected (0.00 sec)

--------------
SELECT id, date_format(tid, '%Y-%m-%dT%H:%M') from rt1
--------------

+------+------------------------------------+
| id   | date_format(tid, '%Y-%m-%dT%H:%M') |
+------+------------------------------------+
|    3 | 2022-01-01T07:00                   |
+------+------------------------------------+
1 row in set (0.00 sec)
--- 1 out of 1 results in 0ms ---

[sanikolaev]

Same with hour():

select hour(tid) from rt1
--------------

+-----------+
| hour(tid) |
+-----------+
|         7 |
+-----------+
1 row in set (0.00 sec)

[sanikolaev]

Another failing test is col_434 when run in the columnar mode - https://github.com/manticoresoftware/columnar/runs/24873252849

[glookka]

These are actually two unrelated issues. One issue is using UTC instead on local timezone on inserts and another issue is treating quoted timestamps as strings that need to be parsed via cctz

[glookka]

Fixed in f6af49b