Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Give access to previous versions' stores in upgrade() functions #1

Open
dfahlander opened this issue Mar 18, 2014 · 0 comments
Open

Comments

@dfahlander
Copy link
Collaborator

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.

dfahlander added a commit that referenced this issue Dec 8, 2016
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.
dfahlander pushed a commit that referenced this issue Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant