| /external/chromium_org/sql/ |
| connection_unittest.cc | 283 // Test that sql::Connection::Raze() results in a database without the
285 TEST_F(SQLConnectionTest, Raze) {
318 ASSERT_TRUE(db().Raze());
336 // Test that Raze() maintains page_size.
359 // After raze, page_size should still match the indicated value.
360 ASSERT_TRUE(db().Raze());
366 // Test that Raze() results are seen in other connections.
377 ASSERT_TRUE(db().Raze());
389 // cause the raze to fail.
396 ASSERT_FALSE(db().Raze());
[all...] |
| recovery.h | 77 // caller should Raze() or otherwise cleanup as appropriate.
105 // diagnostics. Abandon recovery but do not raze the original
165 // |raze| controls whether the original database is razed or just
171 void Shutdown(Disposition raze);
|
| meta_table.h | 27 // |deprecated_version|, raze the database. Must be called outside
31 // may make sense to also raze if meta exists but has no version
|
| meta_table.cc | 38 // Version was out-dated, database raze failed. This user's
101 s.Clear(); // Clear potential automatic transaction for Raze().
103 if (db->Raze()) {
|
| recovery.cc | 111 // TODO(shess): Should Init() failure result in Raze()?
208 // If this is infrequent enough, just wire it to Raze().
235 // run probably should be allowed to try. But since Raze() uses the
255 // strong chance that Raze() would not resolve them. If Delete()
323 void Recovery::Shutdown(Recovery::Disposition raze) {
328 if (raze == RAZE_AND_POISON) {
330 } else if (raze == POISON) {
|
| connection.cc | 73 // Helper to wrap the sqlite3_backup_*() step of Raze(). Return
352 bool Connection::Raze() {
356 DLOG_IF(FATAL, !poisoned_) << "Cannot raze null db";
361 DLOG(FATAL) << "Cannot raze within a transaction";
452 DLOG(FATAL) << "Failed retrying Raze().";
468 DLOG_IF(FATAL, !poisoned_) << "Cannot raze null db";
474 return Raze();
479 DLOG_IF(FATAL, !poisoned_) << "Cannot raze null db";
483 // Raze() cannot run in a transaction.
486 bool result = Raze();
[all...] |
| connection.h | 211 // Raze the database to the ground. This approximates creating a
220 // NOTE(shess): Raze() will DCHECK in the following situations:
225 // Since Raze() is expected to be called in unexpected situations,
236 // so Raze() sets auto_vacuum to 1.
238 // TODO(shess): Raze() needs a connection so cannot clear SQLITE_NOTADB.
241 bool Raze();
253 // Raze() the database and Poison() the handle. Returns the return
254 // value from Raze().
|
| meta_table_unittest.cc | 60 // TODO(shess): It may make sense to Raze() if meta isn't present or
|
| recovery_unittest.cc | 461 // TODO(shess): Should this failure implicitly lead to Raze()?
|
| /external/chromium_org/components/precache/core/ |
| precache_database.cc | 52 // Raze and close the database connection to indicate that it's not usable,
|
| /external/chromium_org/chrome/browser/history/ |
| thumbnail_database.cc | 711 // With that change, this code could Raze() from outside the
[all...] |
| history_database.cc | 240 bool HistoryDatabase::Raze() {
241 return db_.Raze();
|
| history_database.h | 139 bool Raze();
|
| top_sites_database.cc | 229 // to raze the database.
387 if (!db_->Raze())
|
| thumbnail_database_unittest.cc | 712 // databases still need to be handled, perhaps by Raze(), and the
[all...] |
| history_backend.h | 456 // Raze the history database. It will be recreated in a future run. Hopefully
[all...] |
| history_backend.cc | [all...] |
| /external/chromium_org/chrome/browser/extensions/activity_log/ |
| activity_database.h | 163 // transactions, raze the database, and close. When next opened, the
|
| /external/chromium_org/content/browser/net/ |
| sqlite_persistent_cookie_store.cc | 580 db_->Raze();
589 db_->Raze();
609 db_->Raze();
[all...] |
| /external/chromium_org/third_party/sqlite/src/test/ |
| fts1porter.test | [all...] |
