Closed
Bug 1105515
Opened 11 years ago
Closed 9 years ago
explore creating a many-to-many relationship between ``exclusion_profile`` and ``reference_data_signatures`` tables
Categories
(Tree Management :: Treeherder, defect, P5)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: camd, Unassigned)
Details
currently, we store the signatures for an ``exclusion_profile`` in a field of that table called ``flat_exclusions``. This is segregated into the signatures to exclude for each repo.
We could, however, add a new mapping table between ``exclusion_profile`` and ``reference_data_signatures`` rather than storing the signatures in the JSON field.
It wasn't worth doing in my fix for Bug 1074851, but we may want to do that in the future. It's not clear that this would provide any performance improvement during reading.
Updated•11 years ago
|
Priority: -- → P3
Updated•11 years ago
|
Priority: P3 → P5
Comment 1•9 years ago
|
||
getting rid of exclusion profiles
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•