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
In case the previous version's store was removed, and the upgrade function needs to copy items from it, it wont have access to the old store to do that. The use case is that an architecture has changed and objects from one store needs to be copied to another or splitted to several other stores.
There is also a bug in IE that prohibits reading from an object store before deleting the store. If fixing this enhancement we would also need to work around that IE bug by closing and reopening the database towards an intermediate version that would delete the old stores.
The text was updated successfully, but these errors were encountered:
Avoiding the check of the actual backendDB().storeNames if browser has the bug described in issue #1. Needed to get the unit tests though. We might remove this special treatment in the unit tests if we can workaround issue #1.
In case the previous version's store was removed, and the upgrade function needs to copy items from it, it wont have access to the old store to do that. The use case is that an architecture has changed and objects from one store needs to be copied to another or splitted to several other stores.
There is also a bug in IE that prohibits reading from an object store before deleting the store. If fixing this enhancement we would also need to work around that IE bug by closing and reopening the database towards an intermediate version that would delete the old stores.
The text was updated successfully, but these errors were encountered: