This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11164 - There is no way to get from an error event to other objectStores
Summary: There is no way to get from an error event to other objectStores
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jonas Sicking (Not reading bugmail)
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-29 05:44 UTC by Jonas Sicking (Not reading bugmail)
Modified: 2011-03-08 04:19 UTC (History)
3 users (show)

See Also:

Attachments

Description Jonas Sicking (Not reading bugmail) 2010-10-29 05:44:01 UTC 
If inserting data into an objectStore fails, and an error event is dispatched, it is possible to get to the objectStore where the insertion failed, but from there you can't get to the transaction and thus not to the other objectStores.

We should either add .transaction to error events (possibly by mucking with the inheritance chain for IDBTransactionEvent), or by adding .transaction to IDBObjectStore. Possibly we should do both.

Similarly, we might want to add .objectStore on IDBIndex.
Comment 1 Jeremy Orlow 2010-12-10 12:24:00 UTC 
Are you planning on working on this soon?  If not, maybe you should assign it to dave.null@w3.org
Comment 2 Jonas Sicking (Not reading bugmail) 2011-03-08 04:19:58 UTC 
Checked in a fix