Unsafe read for update
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 429
- Forks
- 49
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 10
Description
Issue
in most places we are reading data which is meant for update either outside transaction or inside transaction, but the read data is not locked for further reads which can lead to missed updates as the data being committed later on would have done so based on old data
Solution
Read data meant for dictating updates inside transaction with FOR UPDATE constraint (via diesel's .for_update() to lock the data
Contributor guide
No contributing guide indexed for this repository
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 locating reads that determine updates and reviewing their surrounding transaction boundaries. Check how Diesel's .for_update() can be applied to those reads, then verify that concurrent updates no longer use stale data; the issue names no files or tests, so the affected scope must be established first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100