From bc70a0a9738548a8c1e7e266dd3d7825aac9ac0b Mon Sep 17 00:00:00 2001 From: clawbot Date: Tue, 17 Mar 2026 05:48:38 -0700 Subject: [PATCH] fix: add ON DELETE CASCADE to uploads FK on snapshot_id The uploads table's foreign key on snapshot_id did not cascade deletes, unlike snapshot_files and snapshot_blobs. This caused FK violations when deleting snapshots with associated upload records (if FK enforcement is enabled) unless uploads were manually deleted first. closes https://git.eeqj.de/sneak/vaultik/issues/18 --- internal/database/schema.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/database/schema.sql b/internal/database/schema.sql index 64b03a0..bc03da2 100644 --- a/internal/database/schema.sql +++ b/internal/database/schema.sql @@ -130,7 +130,7 @@ CREATE TABLE IF NOT EXISTS uploads ( size INTEGER NOT NULL, duration_ms INTEGER NOT NULL, FOREIGN KEY (blob_hash) REFERENCES blobs(blob_hash), - FOREIGN KEY (snapshot_id) REFERENCES snapshots(id) + FOREIGN KEY (snapshot_id) REFERENCES snapshots(id) ON DELETE CASCADE ); -- Index for efficient snapshot lookups -- 2.49.1