-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Datetime condition returns inconsistent result #4172
Copy link
Copy link
Closed
Labels
bugConfirmed user-visible misbehaviour in official releaseConfirmed user-visible misbehaviour in official releasecomp-datetimeDate/DateTime/TimeZone datatypes and date-time semantics.Date/DateTime/TimeZone datatypes and date-time semantics.st-acceptedThe issue is in our backlog, ready to takeThe issue is in our backlog, ready to take
Description
select * from reporting_events where device_id = 2 and ts >= '1970-01-01 00:00:00';
SELECT *
FROM reporting_events
WHERE (device_id = 2) AND (ts >= '1970-01-01 00:00:00')
Ok.
0 rows in set. Elapsed: 0.004 sec.
Now, adding 1 day to the string 1970-01-01 00:00:00 and make it 1970-01-02 00:00:00
select * from reporting_events where device_id = 2 and ts >= '1970-01-02 00:00:00';
SELECT *
FROM reporting_events
WHERE (device_id = 2) AND (ts >= '1970-01-02 00:00:00')
┌─id─┬─device_id─┬──────────────────ts─┬─event_hashcode─┬─type─┬─description─┬─is_resolved─┬─resolved_by─┬─────────resolved_at─┬─resolved_comment─┐
│ 40 │ 2 │ 2019-01-28 18:17:08 │ 613812780 │ 4 │ │ 0 │ │ 0000-00-00 00:00:00 │ │
└────┴───────────┴─────────────────────┴────────────────┴──────┴─────────────┴─────────────┴─────────────┴─────────────────────┴──────────────────┘
┌─id─┬─device_id─┬──────────────────ts─┬─event_hashcode─┬─type─┬─description─┬─is_resolved─┬─resolved_by─┬─────────resolved_at─┬─resolved_comment─┐
│ 39 │ 2 │ 2019-01-28 18:17:08 │ -1958892973 │ 0 │ │ 0 │ │ 0000-00-00 00:00:00 │ │
└────┴───────────┴─────────────────────┴────────────────┴──────┴─────────────┴─────────────┴─────────────┴─────────────────────┴──────────────────┘
2 rows in set. Elapsed: 0.005 sec.
CREATE TABLE reporting_events (
id UInt64,
device_id UInt32,
ts DateTime DEFAULT now(),
event_hashcode Int32,
type UInt8,
description String,
is_resolved UInt8,
resolved_by String,
resolved_at DateTime,
resolved_comment String
)
ENGINE = MergeTree()
PARTITION BY toYYYYMM(ts)
ORDER BY (device_id, ts, event_hashcode, type);
I found a similar issue - #2596. However, comparison result seems wrong to me. How it should be handled if this is expected?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugConfirmed user-visible misbehaviour in official releaseConfirmed user-visible misbehaviour in official releasecomp-datetimeDate/DateTime/TimeZone datatypes and date-time semantics.Date/DateTime/TimeZone datatypes and date-time semantics.st-acceptedThe issue is in our backlog, ready to takeThe issue is in our backlog, ready to take