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 10794 - [IndexedDB] Clarify createObjectStore/removeObjectStore's tie to the database setVersion was called on
Summary: [IndexedDB] Clarify createObjectStore/removeObjectStore's tie to the database...
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-09-28 15:30 UTC by Jeremy Orlow
Modified: 2011-06-03 06:05 UTC (History)
4 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-09-28 15:30:12 UTC 
createObjectStore/removeObjectStore are currently on the IDBDatabase object and can only be called while in the middle of a setVersion transaction.  I don't think the spec makes it very clear that they can only be called on the database object where setVersion was called from, however.  Some additional text might be helpful.

This was brought up in this thread: http://www.mail-archive.com/public-webapps@w3.org/msg10431.html (with the subject "[IndexedDB] setVersion with multiple IDBDatabase objects")
Comment 1 Eliot Graff 2011-04-25 18:45:36 UTC 
Assigning to me to edit.
Comment 2 Eliot Graff 2011-06-03 06:05:27 UTC 
Added the following sentences:

]]
The createObjectStore method is tied to the instance of the database that setVersion was called on and can make changes to that database instance only. 

The deleteObjectStore method is tied to the instance of the database that setVersion was called on and can make changes to that database instance only. 
[[

to the following methods:

IDBDatabase.createObjectStore
IDBDatabase.deleteObjectStore
IDBDatabaseSync.createObjectStore
IDBDatabaseSync.deleteObjectStore