From dd595a2ad354e6de45070c1dd97b6f4341da86ae Mon Sep 17 00:00:00 2001 From: Thomas Gelf Date: Tue, 17 Jun 2014 12:47:02 +0000 Subject: [PATCH] Ido/EventHistoryQuery: obsolete raw_timestamp This was never thought to be used in frontends. Frontend code ALWAYS needs to work with unix timestamps, raw timestamps are used internally (e.g. between View and Query) to achieve better search and sort performance. --- .../library/Monitoring/Backend/Ido/Query/EventHistoryQuery.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/monitoring/library/Monitoring/Backend/Ido/Query/EventHistoryQuery.php b/modules/monitoring/library/Monitoring/Backend/Ido/Query/EventHistoryQuery.php index 05b8250f6..477c521fd 100644 --- a/modules/monitoring/library/Monitoring/Backend/Ido/Query/EventHistoryQuery.php +++ b/modules/monitoring/library/Monitoring/Backend/Ido/Query/EventHistoryQuery.php @@ -21,7 +21,7 @@ class EventHistoryQuery extends IdoQuery 'service_description' => 'eho.name2 COLLATE latin1_general_ci', 'object_type' => "CASE WHEN eho.objecttype_id = 1 THEN 'host' ELSE 'service' END", 'timestamp' => 'eh.timestamp', - 'raw_timestamp' => 'UNIX_TIMESTAMP(eh.raw_timestamp)', + 'raw_timestamp' => 'eh.raw_timestamp', // TODO: remove this as soon as removed from frontends 'state' => 'eh.state', 'attempt' => 'eh.attempt', 'max_attempts' => 'eh.max_attempts',