Issue 128623003: IndexedDB: Don't reset cursor prefetches on non-transactional calls

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 128623003: IndexedDB: Don't reset cursor prefetches on non-transactional calls (Closed)

Created:
6 years, 11 months ago by jsbell

Modified:
6 years, 11 months ago

Reviewers:
dgrogan

CC:
chromium-reviews, jsbell, jam, alecflett, joi+watch-content_chromium.org, darin-cc_chromium.org, cmumford, dgrogan

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

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 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=243737