Rewrote the logic for determining which visits should contribute to a suggested page...
commitc1b2efa44d46f948b3820f02e169bd95db094625
authorrfevang@chromium.org <rfevang@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 7 Jun 2012 23:33:30 +0000 (7 23:33 +0000)
committerrfevang@chromium.org <rfevang@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Thu, 7 Jun 2012 23:33:30 +0000 (7 23:33 +0000)
treed294ddd62a47caccbd28e3fe26abe8da6b581cd5
parentde7e8119291898c369b47dac7ba8cd33fc9913f0
Rewrote the logic for determining which visits should contribute to a suggested page's score.

Since I can't ask georgey what the intent behind the old logic was anymore, I rewrote it so that it makes more sense to me. This should also help speed up the query, as well as remove the chance of an infinite loop in the case of cyclic redirect chains.

BUG=125447
TEST=

Review URL: https://chromiumcodereview.appspot.com/10517012

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141116 0039d316-1c4b-4281-b951-d872f2087c98
chrome/browser/history/history_backend.cc
chrome/browser/history/history_backend_unittest.cc
chrome/browser/history/visit_database.cc
chrome/browser/history/visit_database.h
chrome/browser/history/visit_database_unittest.cc