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

Support transaction timeouts #43

Open
inexorabletash opened this Issue Oct 7, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@inexorabletash
Member

inexorabletash commented Oct 7, 2015

Two cases;

  • abort a transaction if it hasn't been able to start before the timeout (e.g. other transactions are holding the lock)
  • abort a transaction if it hasn't attempted to commit before the timeout (i.e. this transaction is too busy)

Chrome does the second automagically in the case of a hung renderer.

Imported from https://www.w3.org/2008/webapps/wiki/IndexedDatabaseFeatures

@kristofdegrave

This comment has been minimized.

Show comment
Hide comment
@kristofdegrave

kristofdegrave Nov 2, 2015

In the first case I would use a blocked callback like when you want to open a newer version of the database and have existing connections. This way you give the developer control on how he wants to act on this

kristofdegrave commented Nov 2, 2015

In the first case I would use a blocked callback like when you want to open a newer version of the database and have existing connections. This way you give the developer control on how he wants to act on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment