Fix: Spurious SQL error message is logged in priming SQLite database cache....

chrome/browser/history/history_database.cc

Index: chrome/browser/history/history_database.cc
===================================================================
--- chrome/browser/history/history_database.cc	(revision 19238)
+++ chrome/browser/history/history_database.cc	(working copy)
@@ -57,8 +57,8 @@
   // Make sure the statement cache is properly initialized.
   statement_cache_->set_db(db_);
 
-  // Prime the cache. See the header file's documentation for this function.
-  PrimeCache();
+  // Prime the cache.
+  MetaTableHelper::PrimeCache(std::string(), db_);
 
   // Create the tables and indices.
   // NOTE: If you add something here, also add it to
@@ -88,19 +88,6 @@
   sqlite3_exec(db_, "PRAGMA locking_mode=EXCLUSIVE", NULL, NULL, NULL);
 }
 
-void HistoryDatabase::PrimeCache() {
-  // A statement must be open for the preload command to work. If the meta
-  // table can't be read, it probably means this is a new database and there
-  // is nothing to preload (so it's OK we do nothing).
-  SQLStatement dummy;
-  if (dummy.prepare(db_, "SELECT * from meta") != SQLITE_OK)
-    return;
-  if (dummy.step() != SQLITE_ROW)
-    return;
-
-  sqlite3Preload(db_);
-}
-
 // static
 int HistoryDatabase::GetCurrentVersion() {
   return kCurrentVersionNumber;