Searched refs:SaveChanges (Results 1 - 11 of 11) sorted by relevance

/external/chromium/chrome/browser/sync/syncable/
H A Dsyncable_unittest.cc181 dir.SaveChanges();
204 dir.SaveChanges();
241 dir.SaveChanges();
293 dir.SaveChanges();
296 // A Directory whose backing store always fails SaveChanges by returning false.
304 virtual bool SaveChanges(const Directory::SaveChangesSnapshot& snapshot) { function in class:syncable::TestUnsaveableDirectory::UnsaveableBackingStore
335 dir_->SaveChanges();
347 dir_->SaveChanges();
467 // Fake SaveChanges() and make sure we got what we expected.
500 // Fake SaveChanges() an
[all...]
H A Ddirectory_backing_store.h47 // 2. Requires that SaveChanges *only* be called from a single thread, and that
52 // SaveChanges is called a new sqlite3 handle is created, and it will get closed
73 // calls SaveChanges *must* be the thread that owns/destroys |this|.
74 virtual bool SaveChanges(const Directory::SaveChangesSnapshot& snapshot);
142 // Lazy creation of save_dbhandle_ for use by SaveChanges code path.
183 // for saving changes periodically via SaveChanges, respectively.
186 // or SyncCore threads, but SaveChanges is always called by the latter. We
H A Ddirectory_manager.cc117 managed_directory_->SaveChanges();
H A Ddirectory_backing_store.cc32 // is calling SaveChanges. In the worst case scenario, the user can put his
350 bool DirectoryBackingStore::SaveChanges( function in class:syncable::DirectoryBackingStore
H A Dsyncable.h730 // When the Directory is told to SaveChanges, a SaveChangesSnapshot is
857 // SaveChanges works by taking a consistent snapshot of the current Directory
862 // internal locking to enforce SaveChanges operations are mutually exclusive.
865 bool SaveChanges();
870 // Get GetUnsyncedMetaHandles should only be called after SaveChanges and
919 // See SaveChanges() for more information.
923 // successfully deleted on disk as a result of the SaveChanges that processed
924 // |snapshot|. See SaveChanges() for more information.
927 // Rolls back dirty bits in the event that the SaveChanges that
1012 // them in here so that SaveChanges ca
[all...]
H A Dsyncable.cc625 bool Directory::SaveChanges() { function in class:syncable::Directory
634 success = store_->SaveChanges(snapshot);
741 // that SaveChanges will at least try again later.
/external/chromium/chrome/browser/sync/glue/
H A Dsync_backend_host.h370 // SaveChanges, close sqlite handles, and halt the syncer thread (which
435 // This must be called from the thread on which SaveChanges is intended to
445 void SaveChanges();
500 // The timer used to periodically call SaveChanges.
H A Dsync_backend_host.cc932 // Initialization is complete, so we can schedule recurring SaveChanges.
1069 this, &Core::SaveChanges); member in class:browser_sync::Core
1081 void SyncBackendHost::Core::SaveChanges() { function in class:browser_sync::SyncBackendHost::Core
1082 syncapi_->SaveChanges();
/external/chromium/chrome/browser/sync/engine/
H A Dsyncapi.cc1238 void SaveChanges();
2767 lookup->SaveChanges();
2790 void SyncManager::SaveChanges() { function in class:sync_api::SyncManager
2791 data_->SaveChanges();
2794 void SyncManager::SyncInternal::SaveChanges() { function in class:sync_api::SyncManager::SyncInternal
2797 DCHECK(false) << "ScopedDirLookup creation failed; Unable to SaveChanges";
2800 lookup->SaveChanges();
H A Dsyncapi.h990 void SaveChanges();
992 // Issue a final SaveChanges, close sqlite handles, and stop running threads.
H A Dsyncer_unittest.cc666 dir->SaveChanges();
694 dir->SaveChanges();

Completed in 1265 milliseconds