Update reverting to the previous value of a field not detected
Bug #277095 reported by
Thomas Herve
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Storm |
Fix Released
|
High
|
Thomas Herve | ||
Bug Description
If a row is cached in 2 stores, that one store change a field value, and the second commit, then change the field value to the original value, then the value in the db is the changed value, not the original one as expected.
Test case coming to clarify
Related branches
lp:~therve/storm/277095-update-cache
- Gustavo Niemeyer: Approve
- James Henstridge: Approve
| Changed in storm: | |
| assignee: | nobody → therve |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Thomas Herve (therve) wrote | #1 |
| Changed in storm: | |
| status: | In Progress → Fix Committed |
| Changed in storm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is ready to review in the attached branch.