[opennms-devel] index on usersNotified

[Jonathan S. <jon...@gm...>]

Hi Chaps,

version 1.15 of create.sql introduced a unique index
userid_notifyid_idx on userID and notifyID of usersnNotified

I don't belive that this is guaranteed to be unique and if it is not,
the installer will fail during a database upgrade.

It is possible with the right notification path, duty schedule and
group combination to have the same user notified multiple times for
the same notice. I know this, because our database has this
combination. This was a result of a sysadmin deputising for the
operations manager and getting a number of escalated notices twice
(once for each role).

I've removed the UNIQUE keyword on line 712 so that installer can
upgrade the database, but I'm not sure of the implications of doing
this. As far as I understand it, the UNIQUE keyword on an index will
create an implicit unique constraint against this table. If this is
used to enforce some logic elsewhere then it could cause trouble.

Cheers .... Jonathan.