schema: unique constraint for import_row_modifier

...priority. Also align current priority to id to get as close as possible
to current fetch order.
This commit is contained in:
Thomas Gelf 2017-08-20 16:00:35 +02:00
parent 41aa86188f
commit 7c18c0b614
4 changed files with 21 additions and 2 deletions

View File

@ -0,0 +1,7 @@
UPDATE import_row_modifier SET priority = id;
ALTER TABLE import_row_modifier ADD UNIQUE INDEX idx_prio (source_id, priority);
INSERT INTO director_schema_migration
(schema_version, migration_time)
VALUES (139, NOW());

View File

@ -1273,6 +1273,7 @@ CREATE TABLE import_row_modifier (
description TEXT DEFAULT NULL,
PRIMARY KEY (id),
KEY search_idx (property_name),
UNIQUE INDEX idx_prio (source_id, priority),
CONSTRAINT row_modifier_import_source
FOREIGN KEY source (source_id)
REFERENCES import_source (id)
@ -1562,4 +1563,4 @@ CREATE TABLE icinga_user_resolved_var (
INSERT INTO director_schema_migration
(schema_version, migration_time)
VALUES (138, NOW());
VALUES (139, NOW());

View File

@ -0,0 +1,9 @@
UPDATE import_row_modifier SET priority = id;
CREATE UNIQUE INDEX import_row_modifier_prio
ON import_row_modifier (source_id, priority);
INSERT INTO director_schema_migration
(schema_version, migration_time)
VALUES (139, NOW());

View File

@ -1416,6 +1416,8 @@ CREATE TABLE import_row_modifier (
);
CREATE INDEX import_row_modifier_search_idx ON import_row_modifier (property_name);
CREATE UNIQUE INDEX import_row_modifier_prio
ON import_row_modifier (source_id, priority);
CREATE TABLE import_row_modifier_setting (
@ -1839,4 +1841,4 @@ CREATE INDEX user_resolved_var_schecksum ON icinga_user_resolved_var (checksum);
INSERT INTO director_schema_migration
(schema_version, migration_time)
VALUES (138, NOW());
VALUES (139, NOW());