From 28c62ddc5acab8531395a38846063ea5f8d2e60d Mon Sep 17 00:00:00 2001 From: TheGeneralist <180094941+thegeneralist01@users.noreply.github.com> Date: Tue, 7 Jul 2026 19:51:27 +0200 Subject: [PATCH] fix: remove ublock_enabled from INSERT OR IGNORE in DDL batch The INSERT ran before the ALTER TABLE migration added the column, causing 'table instance_settings has no column named ublock_enabled' on existing databases. The INSERT OR IGNORE for the default row only needs the original columns; the migration's DEFAULT 1 handles the new column for existing and new rows alike. --- crates/archivr-core/src/database.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/archivr-core/src/database.rs b/crates/archivr-core/src/database.rs index 67439b5..4f2feaf 100644 --- a/crates/archivr-core/src/database.rs +++ b/crates/archivr-core/src/database.rs @@ -469,8 +469,8 @@ pub fn initialize_auth_schema(conn: &Connection) -> Result<()> { INSERT OR IGNORE INTO instance_settings (id, public_index_enabled, public_entry_content_enabled, - public_archive_submission_enabled, default_entry_visibility, ublock_enabled) - VALUES (1, 0, 0, 0, 2, 1); + public_archive_submission_enabled, default_entry_visibility) + VALUES (1, 0, 0, 0, 2); CREATE TABLE IF NOT EXISTS users ( id INTEGER PRIMARY KEY,