Closed utkonos closed 4 days ago
Due to the way these APIs work, Database is actually interacting directly with the DB on disk. Globals are not a part of any snapshot and don't affect the saved/unsaved status. This is intended behavior. Only action item I can think to have for this is a bigger warning about the low-level nature of the Database APIs and how directly they operate.
Version and Platform (required):
Bug Description: If I write a global to the database, the indicator dot on the tab for that database does not show that there are unsaved changes. Additionally, even if the database has not been saved by the user, the global is written to the DB.
Steps To Reproduce:
bv.file.database.write_global('test', 'test')
bv.file.database.globals.get(b'test')
Expected Behavior: The indicaor that unsaved changes appears when the global has been written to the database. And the global is not permanently saved to the database until the user has saved thus committing the change/s.
Screenshots/Video Recording: