Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
set time_zone='Europe/Moscow'; |
create table t1 (a int, d timestamp); |
set @@timestamp=1067121000; |
select now(); |
insert into t1 values (1, current_timestamp()), (2, current_timestamp()); |
set @@timestamp=1067121001; |
update t1 set d= current_timestamp() where a = 2; |
set @@timestamp=1067122860; |
select now(); |
insert into t1 values (3, current_timestamp()), (4, current_timestamp()); |
set @@timestamp=1067122861; |
update t1 set d= current_timestamp() where a = 4; |
select a,d,now(),unix_timestamp(d),unix_timestamp(now()) from t1; |
select a,d,now(),unix_timestamp(d),unix_timestamp(now()) from t1 where d > current_timestamp(); |
drop table t1; |
Attachments
Issue Links
- is blocked by
-
MDEV-16422 DST and unix_timestamp(now())
- Confirmed
- is duplicated by
-
MDEV-16013 During the extra hour upon DST switch historical data from time-versioned tables is shown inconsistently
- Stalled
- relates to
-
MDEV-22828 Bad results near DST change: UNIX_TIMESTAMP(timestamp_column)=<integer literal>
- Open
-
MDEV-32148 Inefficient WHERE timestamp_column=datetime_const_expr
- Closed
-
MDEV-32152 Wrong results near DST for `WHERE indexed_timestamp_column='2010-10-31 02:30:00'`
- Open