Wrap read and write operations within the same transaction on nested set update task
|Category:||Data model / ORM|
|Target version:||Release 2.6.0|
|Google Code Legacy ID:||Tested version:||2.5, 2.6|
The read and write operation on the nested set update task don't happen within a transaction, which may lead to incorrect values if another process modifies the tree at the same time.
#3 Updated by José Raddaoui Marín almost 2 years ago
- Status changed from Code Review to QA/Review
Merged in qa/2.6.x. Apart form verifying that the task works as expected, this one would be hard to test for an analyst, maybe another developer/sys. admin could use MySQL's general log to verify the read and writes are happening in the same transaction (3 transactions by default: IOs, terms and menus).