Create meta table atomically.

chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc

Index: chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc
diff --git a/chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc b/chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc
index bbeb040fd4b98dbecf150b6f75d70361ce1d6af5..6c278116364459a43348e434e0e0076215fb576e 100644
--- a/chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc
+++ b/chrome/browser/net/sqlite_persistent_cookie_store_unittest.cc
@@ -160,9 +160,8 @@ TEST_F(SQLitePersistentCookieStoreTest, TestInvalidMetaTableRecovery) {
     sql::Connection db;
     ASSERT_TRUE(db.Open(temp_dir_.path().Append(chrome::kCookieFilename)));
     sql::MetaTable meta_table_;
-    meta_table_.Init(&db, 0, 0);
-    meta_table_.SetVersionNumber(0);
-    meta_table_.SetCompatibleVersionNumber(0);
+    meta_table_.Init(&db, 1, 1);
+    ASSERT_TRUE(db.Execute("DELETE FROM meta"));

[erikwright (departed), 2012/03/07 14:57:34]

I'd prefer if MetaTable either exposed a 'Delete' method or exposed a kTableName
static member.

[Scott Hess - ex-Googler, 2012/03/07 15:24:27]

I would not be happy exposing such information as part of a non-testing API. 
Exposing it as part of a testing API would effectively mean friending this test,
which to me feels more broken than just going direct.  I think the main goal
should be that this test should break if someone changes the internals of how
sql::MetaTable works, which I think happens here, which will happen, here.

     db.Close();
   }