[dev.icinga.com #3868] Unique key missing for nsm_user_preference

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/3868

Created by mfrosch on 2013-03-17 10:16:18 +00:00

Assignee: mfrosch
Status: Resolved (closed on 2013-03-25 13:54:39 +00:00)
Target Version: 1.8.3
Last Update: 2013-03-25 13:54:39 +00:00 (in Redmine)

Icinga Version: 1.8.4
Icinga Web Version: 1.8.2
IDO Version: 1.8.4
OS Version: Debian/wheezy
DB Type: UNKNOWN
DB Version: ---
Browser Version: ---

---

A unique key on the table nsm_user_preference is missing connecting the fields (upref_user_id, upref_key)

Changesets

2013-03-17 10:17:03 +00:00 by mfrosch aa24c31

SQL Updates for duplicated user_preference data (refs #3868)

for MySQL and PgSQL

in addition the update scripts should cleanup duplicated data

2013-03-17 10:33:11 +00:00 by mfrosch 6bd9c13

SQL Updates for duplicated user_preference data (refs #3868)

for MySQL and PgSQL

in addition the update scripts should cleanup duplicated data

2013-03-17 19:51:09 +00:00 by Tommi 354ffde

Oracle: add new index on nsm_user_preferences and delete duplicates #3870
Refs #3870 #3868

2013-03-17 20:13:59 +00:00 by Tommi 139a247

Oracle: add new unique index on nsm_user_preferences to oracle.sql #3870
Refs #3870 #3868

2013-03-18 11:19:38 +00:00 by Tommi f155ebb

Oracle: bump db_version to 1.8.3 in oracle.sql #3870
Refs #3870 #3868

2013-03-18 19:46:45 +00:00 by Tommi 817a7587796343cbad0bd0a462f974e0e6b30ee3

Oracle: nsm_user_preference use upref_id instead of upref_modified for duplicate check #3870
Refs #3870 #3868

2013-03-25 13:50:27 +00:00 by Tommi c2e3183

Oracle: add new unique index on nsm_user_preferences to oracle.sql #3870
Refs #3870 #3868

2013-03-25 13:50:27 +00:00 by Tommi 1a237b3

Oracle: add new index on nsm_user_preferences and delete duplicates #3870
Refs #3870 #3868

2013-03-25 13:50:28 +00:00 by mfrosch c68f594

Use upref_id instead of upref_modified to fix pgsql data (refs #3868)

2013-03-25 13:50:28 +00:00 by Tommi 88cfa27

Oracle: nsm_user_preference use upref_id instead of upref_modified for duplicate check #3870
Refs #3870 #3868

2013-03-25 13:50:28 +00:00 by Tommi 1f6681c

Oracle: bump db_version to 1.8.3 in oracle.sql #3870
Refs #3870 #3868

2013-03-25 14:15:16 +00:00 by mfrosch b179b1c

Update initial schemas for MySQL and PgSQL (refs #3868)

2013-03-25 15:17:30 +00:00 by Tommi e56097a

Oracle: nsm_user_preference use upref_id instead of upref_modified for duplicate check #3870
Refs #3870 #3868

2013-03-25 15:17:30 +00:00 by mfrosch d08fd83

Use upref_id instead of upref_modified to fix pgsql data (refs #3868)

2013-03-25 15:18:14 +00:00 by mfrosch d191b55

Update initial schemas for MySQL and PgSQL (refs #3868)

---

Relations:

• relates #3727
• relates #3868
• relates #3868

[icinga-migration]

Updated by mfrosch on 2013-03-17 10:45:24 +00:00

• Status changed from Assigned to Resolved
• Done % changed from 0 to 100

We are shipping a SQL schema update which should cleanup duplicated user preferences (including appstate) and introduce a unique constraint on that table to avoid duplication in the future.

Pushed to r1.8 and planned and going to be released with 1.8.3

[icinga-migration]

Updated by mfrosch on 2013-03-18 20:17:57 +00:00

• Status changed from Resolved to Assigned
• Done % changed from 100 to 90

The update scripts might not be good enough, be still could have duplicated keys when the timestamp is the same...

See #3870

[icinga-migration]

Updated by mfrosch on 2013-03-25 13:54:39 +00:00

• Status changed from Assigned to Resolved

MySQL Update should be fine.

PgSQL: Changed the matching key to upref_id instead of upref_modified.

Merged into r1.8