102736 2012-11-19 16:18:41 -0800 IndexedDB: migrate backend Index calls to use transaction ids 2013-01-03 17:08:30 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 102741 P2 Normal --- 102732 102742 104592 99774 1 alecflett alecflett oldest_to_newest 771163 0 alecflett 2012-11-19 16:18:41 -0800 Rather than calling through IDBTransactionBackendInterface, backend index calls should just call through IDBDatabase with a transaction id specifically: (leaving out the details of request/callback hookup/etc) * IDBIndexBackendInterface::openCursor() becomes IDBDatabaseBackendInterface::openCursor(transaction_id, objectstore_id, index_id, direction, key=false); * IDBIndexBackendInterface::openKeyCursor() becomes IDBDatabaseBackendInterface::openCursor(transaction_id, objectstore_id, index_id, direction, key=true); * IDBIndexBackendInterface::count() becomes IDBDatabaseBackendInterface::count(transaction_id, objectstore_id, index_id, keyRange); * IDBIndexBackendInterface::get() becomes IDBDatabaseBackendInterface::get(transaction_id, objectstore_id, index_id, key=false); * IDBIndexBackendInterface::getKey() becomes IDBDatabaseBackendInterface::getKey(transaction_id, objectstore_id, index_id, key=false); 771165 1 alecflett 2012-11-19 16:19:22 -0800 (erp, that last one should have key=true, and both get() and getKey() take a keyRange too) 799856 2 alecflett 2013-01-03 17:08:30 -0800 Decided to just combine these two bugs. *** This bug has been marked as a duplicate of bug 102741 ***