[Activity log] Make database writes in counting policy more robust
Rework the way that new actions are logged in the counting policy so that it properly handles the case where there are duplicate records that weren't properly coalesced. (Duplicate records could arise from clearing URL history, for example.) This comes at the cost of additional queries--an update always takes 2 queries, instead 1 or 2 as before. However, benchmarking shows the cost to be not much different (worst case was ~5% slower, other cases were indistinguishable or even a bit faster). BUG=279465 Review URL: https://chromiumcodereview.appspot.com/23907004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221860 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment