You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optimistic updates in 4.0.1-alpha.13 only sorts results based on index, but the IndexedDB specification requires sorting to be on the combination of index and primary key.
Example: If the query is db.todoItems.where('todoListId').equals(1).toArray(), the index 'todoListId' will be 1 on all results and sorting them on the index won't change any order. The canonical sorting should then be done on the primary key as second sort order.
A fix is on the way...
The text was updated successfully, but these errors were encountered:
Optimistic updates in 4.0.1-alpha.13 only sorts results based on index, but the IndexedDB specification requires sorting to be on the combination of index and primary key.
Example: If the query is
db.todoItems.where('todoListId').equals(1).toArray()
, the index 'todoListId' will be 1 on all results and sorting them on the index won't change any order. The canonical sorting should then be done on the primary key as second sort order.A fix is on the way...
The text was updated successfully, but these errors were encountered: