You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Updated by mfriedrich on 2011-06-16 09:09:00 +00:00
Status changed from New to Assigned
Assigned to set to mfriedrich
hm, i just figured that there's a bug in the oracle code. when starting a downtime, the downtimehistory table was updated twice, but at one spot it should have been the scheduleddowntime table instead.
there's a prepared statement missing for that, which will be added the same as the fixed where was_started=0 in question.
Updated by mfriedrich on 2011-06-16 11:01:34 +00:00
Subject changed from do not update start_time of already started downtimes to do not update start_time of already started downtimes ; fix started downtime update for table scheduleddowntime in oracle
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1658
Created by mfriedrich on 2011-06-16 08:44:44 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2011-06-26 15:33:49 +00:00)
Target Version: 1.4.2
Last Update: 2014-12-08 14:35:51 +00:00 (in Redmine)
requires a rework into mysql/pgsql/oracle.
Attachments
Changesets
2011-06-16 11:03:14 +00:00 by mfriedrich dd24ce3
2011-06-16 11:08:02 +00:00 by mfriedrich 16cea8f
The text was updated successfully, but these errors were encountered: