10027 2010-06-28 20:56:13 +0000 Remove explicit add/remove functions from IDBIndex 2010-10-25 18:12:19 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas nikunj.mehta jorlow mike public-webapps public-webapps-bugzilla oldest_to_newest 36450 0 jonas 2010-06-28 20:56:13 +0000 The spec currently allows entries to be manually added and removed from indexes. While this is one solution to the problem of indexing on computed values, it's not one that seems very popular. There are currently a few other proposals that have been made for example [1] and [2]. Until we figure out how to do more complex indexes, I propose we remove the add/put/remove functions from IDBIndex. Similarly I propose that calling update() on a cursor opened using IDBIndex.openCursor is not allowed. [1] http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/1094.html [2] http://lists.w3.org/Archives/Public/public-webapps/2010AprJun/0882.html 36452 1 jorlow 2010-06-29 05:02:38 +0000 Agreed. Explicitly managed indexes add a lot of surface area and offer nothing that can't be easily emulated with an objectStore. 36758 2 jonas 2010-07-10 21:52:43 +0000 When fixing this, we should decide what to do when IDBCursor.update and IDBCursor.remove does when called on a cursor created using IDBIndex.openCursor. We could either make the functions throw, or make them perform specified change to the objectStore entry that the cursor is referencing. 41736 3 jonas 2010-10-25 18:12:19 +0000 Fixed: http://dvcs.w3.org/hg/IndexedDB/rev/c2618f86a774