102742 2012-11-19 16:50:03 -0800 IndexedDB: stub out Index and ObjectStore calls in IDBDatabaseBackend 2013-01-16 10:08:09 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 104592 P2 Normal --- 102736 102741 1 alecflett webkit-unassigned jsbell oldest_to_newest 771207 0 alecflett 2012-11-19 16:50:03 -0800 We're going to need: (leaving out callbacks) * IDBDatabaseBackendInterface::openCursor(transaction_id, objectstore_id, index_id, keyRange, direction, key); * IDBDatabaseBackendInterface::count(transaction_id, objectstore_id, index_id, keyRange); * IDBDatabaseBackendInterface::get(transaction_id, objectstore_id, index_id, keyRange, key=false); * IDBDatabaseBackendInterface::put(transaction_id, objectstore_id, index_id, key); * IDBDatabaseBackendInterface::deleteFunction(transaction_id, objectstore_id, keyRange); * IDBDatabaseBackendInterface::clear(transaction_id, objectstore_id); * IDBDatabaseBackendInterface::setIndexKeys(transaction_id, objectstore_id, index_ids, index_keys); * IDBDatabaseBackendInterface::setIndexesReady(transaction_id, objectstore_id, index_ids); In a few of these (openCursor and get) you can pass -1 as the index_id and pass true/false to key, to get the getKey/openKeyCursor behavior. We'll likely need more as well, but that covers what is in bug 102741 and bug 102736 808483 1 jsbell 2013-01-16 10:08:09 -0800 *** This bug has been marked as a duplicate of bug 104592 ***