- Notifications
You must be signed in to change notification settings - Fork3.9k
Update indexeddb/article.md - add warning about code rollback#3825
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
CLAassistant commentedMar 19, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Not sure about this.
I think it's already implicit in the warn header (preceding line)
The new warn is a general version management problem and proper testing shoud catch it,
the original explains a really hard to catch issue you shoud be aware of
I think this might be helpful for frontend engineers who are just getting introduced to IndexedDB. Since it’s often their first time working with a stateful system like a database, they may not be familiar with concepts like database migration. In addition, IndexedDB can be especially tricky because it operates outside the developer’s direct control. |
Uh oh!
There was an error while loading.Please reload this page.
add a warning about rollback that might be helpful for developers who are considering indexDB