internal PropertyDatabaseView(PropertyDatabase propertyDatabase, PropertyDatabaseVolatileMemoryStore volatileMemoryStore, PropertyDatabaseMemoryStore memoryStore, PropertyDatabaseFileStore fileStore, PropertyStringTable stringTable, bool delayedSync)
{
m_PropertyDatabase = propertyDatabase;
m_MemoryStore = memoryStore;
m_FileStore = fileStore;
m_VolatileMemoryStoreView = (PropertyDatabaseVolatileMemoryStoreView)volatileMemoryStore.GetView();
m_MemoryStoreView = (PropertyDatabaseMemoryStoreView)memoryStore.GetView();
m_FileStoreView = (PropertyDatabaseFileStoreView)fileStore.GetView();
m_StringTableView = stringTable.GetView(delayedSync);
m_Disposed = false;
m_DelayedSync = delayedSync;
}
public PropertyDatabase(string filePath, bool autoFlush, double backgroundUpdateDebounceInSeconds = k_DefaultBackgroundUpdateDebounceInSeconds)
{
this.filePath = filePath;
stringTableFilePath = GetStringTablePath(filePath);
m_LocalVolatileStore = new PropertyDatabaseVolatileMemoryStore();
m_LocalStore = new PropertyDatabaseMemoryStore();
m_FileStore = new PropertyDatabaseFileStore(filePath);
m_StringTable = new PropertyStringTable(stringTableFilePath, 30);
// Do not allow automatic background updates while running tests. The writing of the file
// causes an assembly leak during the test Unity.IntegrationTests.Scripting.AssemblyReloadTest.AssemblyReloadDoesntLeakAssemblies
// on MacOs. I haven't found out why exactly does the writing of a file causes an assembly to be held, so instead I deactivate
// the automatic update during tests.
this.autoFlush = autoFlush && !Utils.IsRunningTests();
m_Debounce = Delayer.Debounce(_ => TriggerBackgroundUpdate(), backgroundUpdateDebounceInSeconds);
}
public void Dispose()
{
if (m_Disposed)
{
return;
}
if (m_DelayedSync)
{
Sync();
}
m_PropertyDatabase = null;
m_MemoryStore = null;
m_FileStore = null;
m_VolatileMemoryStoreView.Dispose();
m_MemoryStoreView.Dispose();
m_FileStoreView.Dispose();
m_StringTableView.Dispose();
m_DelayedSync = false;
m_Disposed = true;
}
