learningequality / learningequality/studio
duplicate key value violates unique constraint "assessmentitem_unique_keypair_constraint"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Possibly similar/related to #3050, with non-unique email keys
Sentry Issue: STUDIO-EBW
duplicate key value violates unique constraint "assessmentitem_unique_keypair_constraint"
DETAIL: Key (assessment_id, contentnode_id)=(e01b7f2af9d743898aa710027961b450, ecc18984ffc448d085d03864da474845) already exists.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing related issue #3050 and the linked Sentry issue STUDIO-EBW, then trace where the assessment item with the reported assessment_id and contentnode_id is created. Done means identifying the cause of the duplicate key and verifying that the same key pair no longer produces this constraint violation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100