Open
Bug 1347230
Opened 8 years ago
Updated 2 years ago
Investigate ensuring we return correct indices from insertTree (and other APIs?) if we hit races when inserting items
Categories
(Toolkit :: Places, enhancement, P3)
Toolkit
Places
Tracking
()
NEW
People
(Reporter: Gijs, Unassigned)
References
Details
Right now insertTree will always append to the root at which it is inserting. This means user-provided 'index' values are ignored, and we fetch the index at which to insert using a subquery.
This means the insert is always correct (ie items won't have identical indices) but there's no way to know from the jsm what the final index was, without querying the database a second time.
|
||
Updated•8 years ago
|
Priority: -- → P3
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•