[BUG] Database Operations Not Atomic

[olddev94]

Project

vgrep

Description

Database insert operations for files and chunks are not wrapped in transactions. If the process crashes or is interrupted between inserting a file and its chunks, the database will be left in an inconsistent state with orphan records.

Error Message

No error - silent data inconsistency.

Debug Logs

System Information

- Bounty Version: 0.1.0
- OS: Ubuntu 24.04 LTS
- Rust: 1.75+

Screenshots

No response

Steps to Reproduce

1. Start indexing a large directory
2. Kill the process (Ctrl+C, SIGKILL, power failure) during indexing
3. The database may have:
   • Files without chunks (orphan files)
   • Or if using INSERT OR REPLACE, partial re-indexing could lose data

Expected Behavior

1. Use transactions for multi-step operations
2. Either all chunks for a file are inserted, or none
3. Database remains consistent after any crash

Actual Behavior

1. Each INSERT is auto-committed immediately
2. Crash can leave partial data
3. Orphan files or missing chunks possible

Additional Context

No response

[echobt]

Issue validated. The reported problem has been confirmed in the codebase. A Pull Request with the fix has been submitted: CortexLM/vgrep#39.