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.
This commit is contained in:
Thomas Gelf 2014-06-17 12:47:02 +00:00
parent 93e2f36fc8
commit dd595a2ad3
1 changed files with 1 additions and 1 deletions

View File

@ -21,7 +21,7 @@ class EventHistoryQuery extends IdoQuery
'service_description' => 'eho.name2 COLLATE latin1_general_ci', 'service_description' => 'eho.name2 COLLATE latin1_general_ci',
'object_type' => "CASE WHEN eho.objecttype_id = 1 THEN 'host' ELSE 'service' END", 'object_type' => "CASE WHEN eho.objecttype_id = 1 THEN 'host' ELSE 'service' END",
'timestamp' => 'eh.timestamp', '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', 'state' => 'eh.state',
'attempt' => 'eh.attempt', 'attempt' => 'eh.attempt',
'max_attempts' => 'eh.max_attempts', 'max_attempts' => 'eh.max_attempts',