Per sneak's decision on [PR #48](https://git.eeqj.de/sneak/vaultik/pulls/48): remove all ctime from the codebase.
## Scope
1. **Schema**: Remove `ctime` column from `files` table in `internal/database/schema.sql`
2. **Model**: Remove `CTime` field from `database.File` struct
3. **Database layer**: Remove ctime from all SQL queries (INSERT, SELECT) and scan targets in `internal/database/files.go`
4. **Scanner**: Remove `CTime: info.ModTime()` assignment in `checkFileInMemory()` (scanner.go)
5. **README**: Remove any ctime references from schema documentation
## Rationale
- ctime means different things on macOS (birth time) vs Linux (inode change time) — ambiguous cross-platform
- Vaultik never uses ctime operationally (scanning triggers on mtime change)
- Cannot be restored on either platform
- Write-only forensic data with no consumer
Ref: [PR #48 discussion](https://git.eeqj.de/sneak/vaultik/pulls/48)
clawbot
self-assigned this 2026-03-19 13:59:40 +01:00
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.
Per sneak's decision on PR #48: remove all ctime from the codebase.
Scope
ctimecolumn fromfilestable ininternal/database/schema.sqlCTimefield fromdatabase.Filestructinternal/database/files.goCTime: info.ModTime()assignment incheckFileInMemory()(scanner.go)Rationale
Ref: PR #48 discussion