[dev.icinga.com #2089] Timestamps for icinga_slahistory table #790
Comments
Updated by mfriedrich on 2011-11-21 09:29:27 +00:00
and how about pgsql and oracle? their default is not NULL, but still the same value. |
Updated by mfriedrich on 2011-11-23 14:10:37 +00:00
|
Updated by jmosshammer on 2011-11-23 14:20:50 +00:00
PostgreSQL Queries now throw errors in sla (because it requires casts after the tamestamp change. So in 1.6.0. SLA won't be a final feature for all Databases (which isn't that bad, because only the tackle view in ciinga-web currently uses SLA) |
Updated by gbeutner on 2011-11-25 07:54:22 +00:00 Michael: Can you please mention this in the release notes for 1.6? |
Updated by mfriedrich on 2012-02-18 17:23:14 +00:00
please have a look into the postgresql queries and sla. current dev/ido, e586b34
|
Updated by mfriedrich on 2012-04-03 11:01:48 +00:00 probably related to #2203 - though, any updates? |
Updated by mfriedrich on 2012-04-25 16:43:21 +00:00 status? |
Updated by mfriedrich on 2012-04-30 16:11:58 +00:00
this is resolved with #2203 |
Updated by mfriedrich on 2014-12-08 14:35:58 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2089
Created by gbeutner on 2011-11-18 12:36:56 +00:00
Assignee: mfriedrich
Status: Closed (closed on 2012-04-30 16:11:58 +00:00)
Target Version: (none)
Last Update: 2014-12-08 14:35:58 +00:00 (in Redmine)
Hi,
commit 3a56389 (in the gbeutner/sla-test branch) fixes the default values for the start/end/ack timestamps for the slahistory table.
Regards,
Gunnar
Relations:
The text was updated successfully, but these errors were encountered: