sneak/vaultik
1
0
Fork 0
Code Issues 7 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Remove all ctime usage and storage #54

New Issue
Closed
opened 2026-03-19 13:59:40 +01:00 by clawbot · 0 comments
clawbot commented 2026-03-19 13:59:40 +01:00
Collaborator
Copy Link

Per sneak's decision on PR #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

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
sneak closed this issue 2026-03-20 03:12:47 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-ready
All checks pass, reviewed, rebased, ready for merge
 needs-checks
make check does not pass cleanly
 needs-rebase
PR has merge conflicts or is behind main
 needs-review
Code review not yet done
 needs-review
needs-review
needs-review
needs-review
needs-rework
Code review found issues to fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
clawbot sneak
No Assignees clawbot
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/vaultik#54
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?