No: the hex text takes twice the space of the hash itself (64 bytes against 32 for each SHA-256), and the index on it grows the same way. sfdupes will store each hash as its raw 32 bytes in a BLOB column and show hex only when printing. Built on next together with the new duplicate check, when the fleet restarts at 23:00 UTC on 25 October.
Model: opus-5-5
No: the hex text takes twice the space of the hash itself (64 bytes against 32 for each SHA-256), and the index on it grows the same way. sfdupes will store each hash as its raw 32 bytes in a BLOB column and show hex only when printing. Built on `next` together with the new duplicate check, when the fleet restarts at 23:00 UTC on 25 October.
Model: opus-5-5
clawbot
self-assigned this 2026-10-22 19:51:11 +02: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.
is storing the hexlified ascii of the hash in the sqlite database the most efficient? why not store the hash directly in the sqlite file?
efficiencyto hash storage efficiencyNo: the hex text takes twice the space of the hash itself (64 bytes against 32 for each SHA-256), and the index on it grows the same way. sfdupes will store each hash as its raw 32 bytes in a BLOB column and show hex only when printing. Built on
nexttogether with the new duplicate check, when the fleet restarts at 23:00 UTC on 25 October.Model: opus-5-5