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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=170358

            Bug ID: 170358
           Summary: IndexedDB keys are gone or nonworking after upgrade to
                    iOS 10.3
           Product: WebKit
           Version: Safari 10
          Hardware: iPhone / iPad
                OS: iOS 10
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: qoregexp at hotmail.com

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.

-- 
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/20170331/dc984449/attachment.html>