Page MenuHomePhabricator

oresm_model index should not be unique
Closed, ResolvedPublic


Right now I couldn't add new models to ores_model because we already have damaging-0 (a damaging model that is not current) so we can't add more deprecated ones.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Maybe we want to explicitly clean out these rows while we clean up old rows from ores_model before loading in new data.

Just to be clear. We should have two rows per model in ores_model for each model (is_current = 0 and is_current = 1). We should include scores for both of these models in ores_classification but clean out anything older.

Change 309825 had a related patch set uploaded (by Ladsgroup):
Drop unique part from oresm_model index

Change 309825 merged by jenkins-bot:
Drop unique part from oresm_model index