10088 2010-07-05 18:08:01 +0000 The spec does not define what happens if an object store is modified while a cursor is iterating it. 2010-11-08 11:34:59 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 andreip jonas jonas mike public-webapps public-webapps-bugzilla oldest_to_newest 36602 0 andreip 2010-07-05 18:08:01 +0000 It is possible to modify an object store while a cursor is iterating over its objects in the same transaction. Right now, the behavior of the cursor is unspecified. We discussed the 3 solutions for handling this situation: 1. Making the cursor iterate over a snapshot of the data, that is, modifications done during the iteration are not visible when the cursor callbacks fire. The snapshot would be taken when the cursor is created. 2. As 1, except that the snapshot is taken when the transaction starts. 3. Cursors iterate over "live" data and modifications to the object store are visible during the iteration. The consensus for now is to go with solution 3. For pros and cons of each approach as well as motivation for picking the current solution, please see: http://lists.w3.org/Archives/Public/public-webapps/2010JulSep/0056.html 41908 1 jonas 2010-11-01 04:50:50 +0000 Working at rewriting cursor handling, especially related to indexes. 42257 2 jonas 2010-11-08 11:34:59 +0000 Should be fixed by http://dvcs.w3.org/hg/IndexedDB/rev/8716288a4fe1 Would be great if someone could check that it looks correct.