Rebased onto main, resolving merge conflict in internal/vaultik/prune.go.
The conflict arose because PR #41 refactored PruneBlobs() to extract…
60b6746db9
schema: add ON DELETE CASCADE to snapshot_files.file_id and snapshot_blobs.blob_id FKs (#46)
Checked: FK enforcement IS enabled. database.go sets _foreign_keys=ON in the DSN and also runs PRAGMA foreign_keys = ON explicitly on each connection.
So with PRs [#44](https://git.eeqj.de/s…
It depends on whether SQLite FK enforcement is actually enabled. SQLite requires PRAGMA foreign_keys = ON per connection — it's off by default, and many Go SQLite drivers don't enable it…
Yes — the cascades go from parent to junction table:
- Deleting a file → automatically deletes its
snapshot_filesjunction rows (which link files to snapshots) - Deleting a blob →…
Closing: sneak decided to remove ctime entirely rather than fix its population. New issue will track ctime removal from schema, model, and scanner.
Understood. Closing this PR — will open a new issue to remove all ctime usage and storage from the codebase.
You're right, I was wrong about that. Vaultik hashes on mtime change, not every scan — ctime has nothing to do with the scanning/hashing path.
Corrected take: the only value ctime provides is as…
Rework: Rebased onto current main
The branch was based on a stale main (before PR #41 was merged), causing the diff to include reversed…