Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support inter-run caching #18

Open
ssokolow opened this issue Aug 21, 2014 · 0 comments
Open

Support inter-run caching #18

ssokolow opened this issue Aug 21, 2014 · 0 comments

Comments

@ssokolow
Copy link
Owner

In order to streamline the "find dupes, do something manual, re-determine dupes" workflow that often emerges in one-off situations, there should be some way to cache data between runs.

(Something like a --hash-cache=/path/to/file option.)

I'm thinking probably a key-value store which maps inode values to (size, ctime, sha1) triples so that fastdupes can take an rsync-inspired "assume that inode+size+ctime = sha1" shortcut.

(and probably at least starting out SQLite-backed given my bad experiences with shelve corruption, the need for incremental update support, and my aversion to premature optimization.)

@ssokolow ssokolow changed the title Supper inter-run caching Support inter-run caching Aug 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant