Re: [IndexedDB] Consider adding a completion event or callback to the IDBDatabase.close() operation (#72)

Thanks for the information, I was not aware that it was possible to issue additional operations after the first one in the transaction has triggered the `success` event . I thought the transaction would automatically close after one operation has completed and cursors were a special exception to this, carefully designed so they wouldn't run forever (this may help explain my comment on #55).

I'm not here to criticize the IndexedDB design though. That is something that I could go on forever about and at some point I fear would become unpleasant for you to hear.. :) (I could just sum it up: "just start all over"..). Anyway, the level of complexity and sophistication that a working wrapper needs to apply here just to fulfill some basic tasks reliably here is incredible. I feel it is almost a miracle that I managed to develop a working solution that just does what most people want and save them literally  weeks of work needed to overcome the most basic hurdles of figuring out the API approaching a reasonable implementation. 

I will check out some other sources and continue investigating the particular problem in IE11.

Just wanted to also note the MDN docs say an open request doesn't have a transaction property. I usually don't try to rely on browser-specific behaviors so I took it as written. It may be out of date?

https://developer.mozilla.org/en-US/docs/Web/API/IDBRequest 

>IDBRequest.transaction Read only
    The transaction for the request. This property can be null for certain requests, for example those returned from IDBFactory.open (You're just connecting to a database, so there is no transaction to return).

---
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/issues/72#issuecomment-199900041