The FK from snapshot_files.file_id to files.id does NOT cascade. If orphaned files are deleted during cleanup, this will fail. The snapshot_id FK does cascade (from snapshots), but the file_id side does not.
Similarly, snapshot_blobs.blob_id references blobs(id) without CASCADE.
In `schema.sql`:
```sql
CREATE TABLE IF NOT EXISTS snapshot_files (
...
FOREIGN KEY (file_id) REFERENCES files(id)
);
```
The FK from `snapshot_files.file_id` to `files.id` does NOT cascade. If orphaned files are deleted during cleanup, this will fail. The `snapshot_id` FK does cascade (from snapshots), but the `file_id` side does not.
Similarly, `snapshot_blobs.blob_id` references `blobs(id)` without CASCADE.
Ref: parent issue #1
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In
schema.sql:The FK from
snapshot_files.file_idtofiles.iddoes NOT cascade. If orphaned files are deleted during cleanup, this will fail. Thesnapshot_idFK does cascade (from snapshots), but thefile_idside does not.Similarly,
snapshot_blobs.blob_idreferencesblobs(id)without CASCADE.Ref: parent issue #1