IndexedDB: Don't reset cursor prefetches on non-transactional calls
Cursor prefetch caches must be reset when requests that could invalidate the cache are made (i.e. puts, deletes), and to ensure that requests are processed in order per spec (i.e. even gets). This doesn't apply to requests that aren't scoped to a transaction, so some unnecessary resets can be removed. BUG=329950 R=dgrogan Review URL: https://codereview.chromium.org/128623003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243737 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment