owner:rcross@amsl.com resolution_fixed type_defect | by rcross@amsl.com
There is a uniqueness constraint for ReviewSettings. One per person per team. If both Persons being merged have ReviewerSettings for the same team, one will need to be dropped with the merge.
RJS:
I think you should keep the one that goes with the person record you are merging into.
But you might also skim the migration here for ideas: https://trac.tools.ietf.org/tools/ietfdb/browser/personal/jennifer/7.24.1.dev1/ietf/review/migrations/0027_unique_constraint_for_reviewersettings.py?rev=18833
Issue migrated from trac:3183 at 2022-03-04 08:10:07 +0000
owner:rcross@amsl.comresolution_fixedtype_defect| by rcross@amsl.comThere is a uniqueness constraint for ReviewSettings. One per person per team. If both Persons being merged have ReviewerSettings for the same team, one will need to be dropped with the merge.
RJS:
I think you should keep the one that goes with the person record you are merging into.
But you might also skim the migration here for ideas: https://trac.tools.ietf.org/tools/ietfdb/browser/personal/jennifer/7.24.1.dev1/ietf/review/migrations/0027_unique_constraint_for_reviewersettings.py?rev=18833
Issue migrated from trac:3183 at 2022-03-04 08:10:07 +0000