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

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webkit-unassigned
Subject:    [Webkit-unassigned] [Bug 170358] New: IndexedDB keys are gone or nonworking after upgrade to iOS 10.
From:       bugzilla-daemon () webkit ! org
Date:       2017-03-31 21:03:51
Message-ID: bug-170358-2851 () https ! bugs ! webkit ! org/
[Download RAW message or body]

--Boundary_(ID_LMx0H4eIIAPxLx2ccc3szQ)
Date: Fri, 31 Mar 2017 14:03:54 -0700
Auto-submitted: auto-generated
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Bugzilla-URL: https://bugs.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@lists.webkit.org
          Reporter: qoregexp@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.

--Boundary_(ID_LMx0H4eIIAPxLx2ccc3szQ)
Date: Fri, 31 Mar 2017 14:03:54 -0700
Auto-submitted: auto-generated
MIME-version: 1.0
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Bugzilla-URL: https://bugs.webkit.org/

<html>
    <head>
      <base href="https://bugs.webkit.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - IndexedDB keys are gone or nonworking after upgrade to iOS 10.3"
   href="https://bugs.webkit.org/show_bug.cgi?id=170358">170358</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>IndexedDB keys are gone or nonworking after upgrade to iOS 10.3
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>WebKit
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>Safari 10
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>iPhone / iPad
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>iOS 10
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>Major
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P2
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>WebCore Misc.
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>webkit-unassigned&#64;lists.webkit.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>qoregexp&#64;hotmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>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.</pre>  </div>
      </p>

      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>

--Boundary_(ID_LMx0H4eIIAPxLx2ccc3szQ)--

_______________________________________________
webkit-unassigned mailing list
webkit-unassigned@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-unassigned

[prev in list] [next in list] [prev in thread] [next in thread] 