IndexedDB: Indexes created after data are added are sometimes improperly populated

RESOLVED FIXED

Status

()

Product:
Core
Component:
DOM: IndexedDB
Status:
RESOLVED FIXED
Reported:
8 years ago
Modified:
7 years ago

People

(Reporter: bent.mozilla, Assigned: bent.mozilla)

Tracking

Version:
unspecified
Points:
---

Firefox Tracking Flags

(blocking2.0 final+)

Details

(Whiteboard: [softblocker])

Attachments

(1 attachment)

Patch, v1
8.57 KB, patch
sicking
: review+
Details | Diff | Splinter Review
(Assignee)

Description

•
8 years ago
Posted patch Patch, v1 — — 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

•
8 years ago 
This does not need beta coverage, blocking final is all it needs.
blocking2.0: ? → final+
Whiteboard: [softblocker]
 (Assignee)

Comment 2

•
8 years ago 
http://hg.mozilla.org/mozilla-central/rev/c30066b12743
Status: ASSIGNED → RESOLVED
Last Resolved: 8 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.