11947 2011-02-01 17:54:29 +0000 [IndexedDB] Updating object stores with auto increment 2011-02-04 10:33:39 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC Linux RESOLVED DUPLICATE 11976 P2 normal --- 1 hans dave.null jorlow mike public-webapps public-webapps-bugzilla oldest_to_newest 44978 0 hans 2011-02-01 17:54:29 +0000 In 5.1 Object Store Storage Operation, step 1 it says: "If store uses a key generator and key is undefined, set key to the next generated key. If store also uses in-line keys, then set the property in value pointed to by store's key path to the new value for key". But in the object store example in 3.3.3, there is the following: A second put operation will overwrite the record stored by the first put operation. var abraham = {id: 1, name: 'Abraham', number: '2107'}; store.put(abraham); However, the way I read the specification, the key generator will generate the key 2, and then set the "id" property in the value to 2. So this operation does not at all overwrite the first record, and the next statement in the example: "Now when the object store is read with the same key, the result is different compared to the object read earlier." is false. To me, it would make sense that: 1. If a user provides an explicit key to an operation on an object store that has a key generator, then the explicit key takes precedence, and the key generator doesn't do anything. 2. If a user provides an in-line key, then that key takes precedence, and the key generator doesn't do anything. 45121 1 hans 2011-02-04 10:33:39 +0000 *** This bug has been marked as a duplicate of bug 11976 ***