10064 2010-07-02 09:40:54 +0000 Modifying functions should throw when called under invalid conditions 2010-07-02 20:01:54 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas andreip mike public-webapps public-webapps-bugzilla oldest_to_newest 36533 0 jonas 2010-07-02 09:40:54 +0000 There are a number of situations where we immediately upon call to modifying functions know that the call was made in error without consulting the database. This applies in the following situations: 1. When IDBObjectStore.add, IDBObjectStore.put, IDBObjectStore.remove, IDBCursor.update or IDBCursor.remove is called from a READ_ONLY transaction. 2. When the object provided to add/put/update can't be cloned using the structured clone algorithm. (we can rely on HTML5 to define when and what this throws) 3. When IDBCursor.update is called in such a way that it alters the key of the object. (only apples to in-line keys) 4. When IDBObjectStore.add or IDBObjectStore.put is called on an objectStore which doesn't use a key generator, and no key is provided (note that keys are supplied in-line in some stores) For more details about rationale, see the thread started at http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0002.html 36542 1 andreip 2010-07-02 20:01:54 +0000 Fixed in http://dvcs.w3.org/hg/IndexedDB/rev/e039f9694056 http://dvcs.w3.org/hg/IndexedDB/rev/0ac9282957a0