yesodweb / yesodweb/persistent
deleteBy is broken in some cases
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 486
- Forks
- 306
- PR merge metrics
- No merged PRs in 30d
Description
Function deleteBy is broken in cases where at least one of the fields of composite unique key is nullable.
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 at the deleteBy entry point and trace how composite unique keys with nullable fields are handled. Reproduce the reported case, then identify the relevant tests or add a focused regression test; done means deleteBy works correctly when at least one composite-key field is nullable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100