- the problem: my movie library on several drives, moves that half-finish, no undo
- the rule I set: never delete a file unless the user explicitly asks
- journal first: write every planned step to SQLite before touching the disk
- the copy: pipelined reader/writer, flush, read back past the OS cache, compare SHA-256
- the switch: staging folder → one rename → library points at the new place
- originals to the recycle bin / freedesktop trash (rename-only, never copied)
- undo from history, and what happens after a crash mid-move
- try it / contribute: https://github.com/mustafayevt/CineVault
Database
Source:https://dev.to/tural_mustafayev_250bf82c/how-i-made-file-moves-between-drives-undoable-and-verified-in-a-rust-desktop-app-17ib
How I made file moves between drives undoable and verified in a Rust desktop app
dev.to Rust0 views
PreviousFreeze a Real Run into a Corpus: How Baize Scores Agents with Deterministic EvidenceNextCancelling timers with AbortController: seven cases including cleanup
Related posts
I Cut 2,000 Flushes to Zero and fsync Still Returned Success
0dev.to Linux
Magnus Hagander: Nordic PGDay 2027 - Sponsorships for Nordic PGDay 2027 Are Now Open
0Planet PostgreSQL
SOLID Principles Explained: 5 Essential Principles for Writing Clean, Maintainable Code
0dev.to Tutorial
How to Build a Professional Resume in 2026: Best Resume Formats, Templates, and ATS Tips
0dev.to Career
How to Explain Your Project in a Technical Interview
0dev.to Career
Stop Calling It "Refactoring" When You Are Just Moving The Bugs Around
0dev.to Career