fix: add ON DELETE CASCADE to uploads FK on snapshot_id
All checks were successful
check / check (pull_request) Successful in 4m15s

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 #18
This commit is contained in:
clawbot
2026-03-17 05:48:38 -07:00
parent c24e7e6360
commit bc70a0a973

View File

@@ -130,7 +130,7 @@ CREATE TABLE IF NOT EXISTS uploads (
size INTEGER NOT NULL, size INTEGER NOT NULL,
duration_ms INTEGER NOT NULL, duration_ms INTEGER NOT NULL,
FOREIGN KEY (blob_hash) REFERENCES blobs(blob_hash), 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 -- Index for efficient snapshot lookups