Details
-
Task
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
create or replace table t1 (a timestamp); |
insert t1 values ('2018-3-25 1:30:00'); |
create or replace table t2 as select a + interval 1 hour from t1; |
show create table t2; |
returns
+-------+----------------------------------------------------------------------------------------------------------+
|
| Table | Create Table |
|
+-------+----------------------------------------------------------------------------------------------------------+
|
| t2 | CREATE TABLE `t2` (
|
`a + interval 1 hour` datetime DEFAULT NULL
|
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
|
+-------+----------------------------------------------------------------------------------------------------------+
|
Should be timestamp, not datetime.
This should cover all temporal arithmetic functions, e.g. ADDTIME too.
Attachments
Issue Links
- duplicates
-
MDEV-25279 Time operations do not consider daylight savings
- Closed
- is blocked by
-
MDEV-15751 CURRENT_TIMESTAMP should return a TIMESTAMP (WITH TIME ZONE?)
- In Testing
-
MDEV-16852 Get rid of Item_temporal_hybrid_func::fix_temporal_type()
- Closed
-
MDEV-16864 Implement class Item_func_timestamp
- Closed
-
MDEV-16874 Implement class Item_handled_func
- Closed
-
MDEV-32496 TIMESTAMP variant to support YEAR range -4713 and +9999
- Open
- relates to
-
MDEV-15751 CURRENT_TIMESTAMP should return a TIMESTAMP (WITH TIME ZONE?)
- In Testing
-
MDEV-15654 ADDTIME creates invalid timestamp value near DST changes
- Closed
-
MDEV-30633 DATETIME to TIMESTAMP conversion to return maximum timestamp on overflow
- Stalled
-
MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range
- Closed