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 11113 - [IndexedDB] The spec should be more explicit about the queuing of setVersion transactions
Summary: [IndexedDB] The spec should be more explicit about the queuing of setVersion ...
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: Eliot Graff
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-21 14:58 UTC by Jeremy Orlow
Modified: 2011-06-06 21:06 UTC (History)
5 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-10-21 14:58:43 UTC 
The resolution of the "[IndexedDB] Calling setVersion while already in a setVersion transaction" thread was that calling setVersion while in another setVersion transaction should simply queue up another setVersion transaction to run when the current is finished.  It'd be nice if the spec could make this more explicit.
Comment 1 Jonas Sicking (Not reading bugmail) 2010-10-29 23:08:20 UTC 
I *think* this might be strictly defined now by

http://dvcs.w3.org/hg/IndexedDB/rev/26e7d99ab935

But we could certainly make it more explicit in the setVersion() function definition or some such. Probably need to do the same for transaction().
Comment 2 Eliot Graff 2011-04-25 18:47:01 UTC 
assigning to me to make the suggested edit
Comment 3 Eliot Graff 2011-06-06 21:06:20 UTC 
Added the following sentence to IDBDatabaseSync.setVersion()

]]
Calling setVersion() while a first setVersion transaction is already running queues up another setVersion transaction to run after the first setVersion transaction is finished. 
[[