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 2013-09-14 15:19:33 +00:00
Subject changed from comments UK misses object_id, not allowing the same comment on host AND service to comments(history) UK misses object_id, not allowing the same comment on host AND service
This issue has been migrated from Redmine: https://dev.icinga.com/issues/4544
Created by mfriedrich on 2013-08-12 08:12:06 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2013-09-14 15:21:30 +00:00)
Target Version: 1.10
Last Update: 2014-12-08 14:36:00 +00:00 (in Redmine)
given that you may assign a comment id to a host AND a service the following unique constraint will trigger
which is obviously incorrect as the column "comment_type" is not taken into account (nor the object_id).
for the scheduleddowntime table this seems correct
as the object_id is different for the host and the service then.
it does not affect 1.x as there are no shared comment ids but it hurts future designs like icinga2 compat.
Changesets
2013-09-14 15:20:49 +00:00 by (unknown) ce91b9d
Relations:
The text was updated successfully, but these errors were encountered: