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

IdbVersionChangeEvent should expose the current IdbTransaction #20

Closed
zecakeh opened this issue Mar 4, 2023 · 3 comments · Fixed by #26
Closed

IdbVersionChangeEvent should expose the current IdbTransaction #20

zecakeh opened this issue Mar 4, 2023 · 3 comments · Fixed by #26
Labels
Released This issue's resolution is now available in a published release

Comments

@zecakeh
Copy link

zecakeh commented Mar 4, 2023

This event is fired during a transaction with mode versionchange, which should be available in event.target.transaction.

Although accessing the IdbDatabase allows us to create/delete object stores and set their indexes, it doesn't allow to access current stores. We need to access them via the IdbTransaction.

It would allow to change the indexes of the existing object stores, and to fix data in the stores or even migrate data from one store to the other.

@kurtbuilds
Copy link
Contributor

I created a PR that exposes this API:

#26

Alorel pushed a commit to kurtbuilds/indexed_db_futures that referenced this issue Oct 28, 2023
Alorel pushed a commit that referenced this issue Oct 28, 2023
@Alorel
Copy link
Owner

Alorel commented Oct 29, 2023

And it's released 🙂

@kurtbuilds
Copy link
Contributor

Amazing turn around time! Thank you

@Alorel Alorel added the Released This issue's resolution is now available in a published release label Oct 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Released This issue's resolution is now available in a published release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants