Closed
Bug 628063
Opened 15 years ago
Closed 15 years ago
IndexedDB: Indexes created after data are added are sometimes improperly populated
Categories
(Core :: Storage: IndexedDB, defect)
Core
Storage: IndexedDB
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
People
(Reporter: bent.mozilla, Assigned: bent.mozilla)
Details
(Whiteboard: [softblocker])
Attachments
(1 file)
|
8.57 KB,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
Oops. This is bad, we don't handle index creation after data are added in two cases:
1. The index name != the indexed property name (forehead slap, idiocy).
2. The indexed property is an integer rather than a string.
Both are bad, and now fixed. Our tests magically missed *both* of these cases :(
Attachment #506159 -
Flags: review?(jonas)
|
Assignee | |
Comment 1•15 years ago
|
||
This does not need beta coverage, blocking final is all it needs.
Attachment #506159 -
Flags: review?(jonas) → review+
blocking2.0: ? → final+
Whiteboard: [softblocker]
|
|
Assignee | |
Comment 2•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: DOM → DOM: IndexedDB
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•