RESOLVED FIXED 107311
IndexedDB: Switch to new createTransaction call
https://bugs.webkit.org/show_bug.cgi?id=107311
Summary IndexedDB: Switch to new createTransaction call
Alec Flett
Reported 2013-01-18 12:17:49 PST
IndexedDB: Switch to new createTransaction call
Attachments
Patch (22.86 KB, patch)
2013-01-18 12:23 PST, Alec Flett
no flags
Patch (22.06 KB, patch)
2013-01-18 14:02 PST, Alec Flett
no flags
Patch for landing (22.12 KB, patch)
2013-01-18 15:38 PST, Alec Flett
no flags
Alec Flett
Comment 1 2013-01-18 12:23:46 PST
Alec Flett
Comment 2 2013-01-18 12:24:51 PST
jsbell / dgrogan - have a look? This won't pass tests until the chromium side lands.
Joshua Bell
Comment 3 2013-01-18 13:23:46 PST
Comment on attachment 183525 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=183525&action=review overall lgtm > Source/WebCore/ChangeLog:10 > + transaction objects. This allows an asynchronous call in Chromium Replace "Chromium" with "multiprocess ports". > Source/WebCore/ChangeLog:15 > + No new tests (OOPS!). Replace the OOPS! (or it won't commit). > Source/WebKit/chromium/ChangeLog:6 > + Reviewed by NOBODY (OOPS!). Ditto. > Source/WebCore/Modules/indexeddb/IDBDatabaseBackendImpl.cpp:667 > + LOG_ERROR("Not committing aborted transaction %ld", transactionId); Shouldn't LOG_ERROR here, since this is expected behavior. and the LOG doesn't tell us or a developer/user anything actionable. I think the comment/code in abort() (below) is a better approach. > Source/WebCore/Modules/indexeddb/IDBDatabaseBackendImpl.cpp:1161 > // FIXME: Remove this method in https://bugs.webkit.org/show_bug.cgi?id=103923. Can't this method be removed now, just leaving the stub in WebKit/chromium/public? > Source/WebCore/Modules/indexeddb/IDBDatabaseCallbacksImpl.cpp:76 > + ASSERT(!(transactionId >> 32)); Do these ASSERTs belong in WebCore are they just enforcing how Chromium uses the IDs? (i.e. maybe move them into WebKit/chromium/src) > Source/WebCore/Modules/indexeddb/IDBTransaction.h:151 > // FIXME: Remove references to the backend when the backend is fully flattened: https://bugs.webkit.org/show_bug.cgi?id=99774 Remove this comment?
Alec Flett
Comment 4 2013-01-18 14:02:20 PST
Alec Flett
Comment 5 2013-01-18 14:03:29 PST
Comment on attachment 183543 [details] Patch tony@ - r? jsbell: I have a bunch of code to remove and I was going to get it all in a WebKit API-oriented patch, so I'll take care of removing the old createTransaction then.
Alec Flett
Comment 6 2013-01-18 14:03:57 PST
[trying that again] tony@ - r?
WebKit Review Bot
Comment 7 2013-01-18 14:06:15 PST
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
WebKit Review Bot
Comment 8 2013-01-18 14:21:17 PST
Comment on attachment 183543 [details] Patch Attachment 183543 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/15938833
Peter Beverloo (cr-android ews)
Comment 9 2013-01-18 15:18:11 PST
Comment on attachment 183543 [details] Patch Attachment 183543 [details] did not pass cr-android-ews (chromium-android): Output: http://queues.webkit.org/results/15937919
Alec Flett
Comment 10 2013-01-18 15:38:02 PST
Created attachment 183561 [details] Patch for landing
WebKit Review Bot
Comment 11 2013-01-18 16:45:24 PST
Comment on attachment 183561 [details] Patch for landing Clearing flags on attachment: 183561 Committed r140219: <http://trac.webkit.org/changeset/140219>
WebKit Review Bot
Comment 12 2013-01-18 16:45:28 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.