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

Question: How to correctly manage structure changes #46

Closed
localnerve opened this issue Mar 18, 2016 · 1 comment
Closed

Question: How to correctly manage structure changes #46

localnerve opened this issue Mar 18, 2016 · 1 comment

Comments

@localnerve
Copy link

This isn't really a treo issue or question, per se, more an IndexedDB question from a noob.

What is the proper way to handle structure changes?

For example, new objectStores are only added in schema.callback (onupgradeneeded), which does not fire by just simply adding a new store via schema.addStore.

The MDN docs suggests that you just bump the version to trigger the event.

Is that what treo expects a user to do?
Then what about the old version? must drop it? How does version growth get managed?

Thanks for taking the time to read my question.
I apologize if this is inappropriate.

@localnerve
Copy link
Author

After reading MDN more, I get it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant