[Webkit-unassigned] [Bug 170358] IndexedDB keys are gone or nonworking after upgrade to iOS 10.3

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Apr 2 18:04:08 PDT 2017


--- Comment #2 from Brady Eidson <beidson at apple.com> ---
(In reply to Meredith Anderson from comment #0)
> IndexedDB data retrieval by key stops working if an existing database is
> upgraded to iOS 10.3.  For example, for a table that has a numeric primary
> key and a unique string secondary key, attempts to retrieve records either
> by the primary key or the secondary key return undefined.  I was able to
> determine that the data itself is still there by doing a retrieval of all
> data.  The fields that are used as keys have values, but I don't know what
> the state of the key structures themselves is, whether they are gone or
> pointing to the wrong place now.  I'm using Dexie so I can't give you the
> native indexedDB syntax, but it's easy to reproduce.  If the database is
> created under iOS 10.3, there isn't a problem.  It's something happening in
> the upgrade.

There's definitely a new storage format for keys on disk, but we also definitely handle the only key format.

I can demonstrate with a simple local test case that we do handle legacy key lookups fine.

Even though you saw this with Dexie and therefore don't have the raw IDB, can you please include a minimal Dexie test case?

I can find out the raw IDB from that.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170403/5b1bbdb1/attachment.html>

More information about the webkit-unassigned mailing list