Actions
Bug #14007
closedIndexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Indexes on nodecompliancelevels are not valid: we have 3 time the same index
CREATE INDEX nodecompliancelevels_nodeId ON nodecompliancelevels (nodeId); CREATE INDEX nodecompliancelevels_ruleId ON nodecompliancelevels (nodeId); CREATE INDEX nodecompliancelevels_directiveId ON nodecompliancelevels (nodeId);
Updated by Nicolas CHARLES about 6 years ago
- Related to Architecture #12621: Explore alternative format for compliance table added
Updated by Nicolas CHARLES about 6 years ago
- Subject changed from indexes on nodecompliancelevels table are not valid to indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES about 6 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES about 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2101
Updated by Nicolas CHARLES about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|705d70c64aeb10c735188c2c4b2b92b419369e94.
Updated by Vincent MEMBRÉ almost 6 years ago
- Status changed from Pending release to Released
Updated by Alexis Mousset almost 6 years ago
- Subject changed from indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used to Indexes on nodecompliancelevels table are not valid and table ArchivedReportsExecution is never used
Actions