Add Optimistic Locking in Future
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
http://railscasts.com/episodes/59-optimistic-locking-revised?view=asciicast
Prevents updates to the same entry simultaneously from two sessions from screwing up stuff
Not necessary at this point in time because our admin side usage is low.
KIV for future addition.
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the linked Railscasts episode first to understand the intended optimistic-locking behavior. The issue names no files, tests, or entry points, and explicitly defers the work because admin usage is currently low. Done criteria and implementation scope would need to be established before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100