From dc157cccd5180e63c4980044c85a0d055391d91c Mon Sep 17 00:00:00 2001 From: dgtlmoon Date: Sat, 7 Feb 2026 02:20:51 +0100 Subject: [PATCH] remove old code --- changedetectionio/store/base.py | 15 --------------- changedetectionio/store/file_saving_datastore.py | 10 ---------- 2 files changed, 25 deletions(-) diff --git a/changedetectionio/store/base.py b/changedetectionio/store/base.py index 5627e4d9e..38f3af226 100644 --- a/changedetectionio/store/base.py +++ b/changedetectionio/store/base.py @@ -81,18 +81,3 @@ class DataStore(ABC): """ pass - @abstractmethod - def force_save_all(self): - """ - Force immediate synchronous save of all data to storage. - - This is the abstract method for forcing a complete save. - Different backends implement this differently: - - File backend: No-op (watches save immediately via commit()) - - Redis backend: SAVE command or pipeline flush - - SQL backend: COMMIT transaction - - Note: With immediate persistence, this is mostly a no-op for file backend. - Used for backward compatibility. - """ - pass diff --git a/changedetectionio/store/file_saving_datastore.py b/changedetectionio/store/file_saving_datastore.py index b652342bb..59a0ea38c 100644 --- a/changedetectionio/store/file_saving_datastore.py +++ b/changedetectionio/store/file_saving_datastore.py @@ -350,16 +350,6 @@ class FileSavingDataStore(DataStore): """ raise NotImplementedError("Subclass must implement _save_settings") - def force_save_all(self): - """ - Deprecated: Watches now save immediately via commit(). - - Kept as no-op for backward compatibility. In the old system, - this would force all watches to save. With immediate persistence, - all changes are already saved. - """ - logger.info("force_save_all() called - no-op (immediate persistence enabled)") - pass def _load_watches(self): """