Skip to content

feat: make datatracker_person_id unique - #1294

Draft
rudimatz wants to merge 1 commit into
ietf-tools:mainfrom
rudimatz:feat/make-datatracker-person-ID-unique
Draft

feat: make datatracker_person_id unique#1294
rudimatz wants to merge 1 commit into
ietf-tools:mainfrom
rudimatz:feat/make-datatracker-person-ID-unique

Conversation

@rudimatz

@rudimatz rudimatz commented May 25, 2026

Copy link
Copy Markdown
Contributor

fixes #1283

make field datatracker_person_id unique

@jennifer-richards

Copy link
Copy Markdown
Member

Capturing a brief discussion: imo this would be a good change. Before committing to it, though, we need to think a bit more about how we'll deal with datatracker person merges. The code this PR changes was speculatively written to allow for merges to be handled by pointing multiple DatatrackerPerson records at the same datatracker_id. It's not clear if we'll actually want to do that, though.

ietf-tools/datatracker#10558 has a proposal to add multiple IDs per datatracker Person so that after a merge, the UUIDs associated with either of the pre-merge Person records are associated with the post-merge Person. This, or a similar approach, might avoid purple needing to update its records after a merge. (It may not, though, and need to work through the issue before drawing a firm conclusion.)

@rudimatz
rudimatz marked this pull request as draft May 25, 2026 18:47
@rudimatz rudimatz changed the title feat: make datattracker_person_id unique feat: make datatracker_person_id unique Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot assign a FinalApproval to a person not already known to the purple system

2 participants