Re: [w3c/IndexedDB] Add IDBTransaction commit() method (#242)

Commenting here for the record:

@inexorabletash, @dmurph, and I discussed how to handle requests with errors on them in the context of explicit commit. The primary question dealt with the cases in which an explicitly committed transaction with errored requests should be aborted versus allowed to commit. 

The upshot was an agreement that if, at the time the backend receives a commit signal, the backend is certain that any and all errors on requests belonging to a transaction have been handled in onerror events on the frontend, then that transaction can be committed, otherwise it should be aborted. This is summarized in the attached diagrams.

![explicit_commit_error_abort](https://user-images.githubusercontent.com/43356805/49839973-4b806f80-fd66-11e8-80d4-f7fda05bb8cf.png)

![explicit_commit_error_commit](https://user-images.githubusercontent.com/43356805/49839980-55a26e00-fd66-11e8-97da-b43100feadff.png)

![explicit_commit_error_maybe](https://user-images.githubusercontent.com/43356805/49839986-5f2bd600-fd66-11e8-866c-1af74f4319c3.png)

 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/pull/242#issuecomment-446421869