From 3c015bf8228f68ba45c6f4f8472c6d26d3874c8e Mon Sep 17 00:00:00 2001 From: gtsiam Date: Thu, 3 Oct 2024 04:34:14 +0300 Subject: [PATCH] Do not migrate db to new config path (#14123) I just saw this, and I would be very surprised by that behaviour as a user. Changing the db path would randomly move the database, and changing it back (or to anything, really) would not. These kinds of advanced settings are generally expected to do one thing: Change the path frigate opens the database from. The end. --- frigate/app.py | 8 -------- 1 file changed, 8 deletions(-) diff --git a/frigate/app.py b/frigate/app.py index a04c4737e..ca419e045 100644 --- a/frigate/app.py +++ b/frigate/app.py @@ -35,7 +35,6 @@ from frigate.const import ( CACHE_DIR, CLIPS_DIR, CONFIG_DIR, - DEFAULT_DB_PATH, EXPORT_DIR, MODEL_CACHE_DIR, RECORD_DIR, @@ -151,13 +150,6 @@ class FrigateApp: except PermissionError: logger.error("Unable to write to /config to save DB state") - # Migrate DB location - old_db_path = DEFAULT_DB_PATH - if not os.path.isfile(self.config.database.path) and os.path.isfile( - old_db_path - ): - os.rename(old_db_path, self.config.database.path) - # Migrate DB schema migrate_db = SqliteExtDatabase(self.config.database.path)