I'd like to suggest adding the ability to match for md5 and crc32 to the advanced search box.
MD5 support is already present in other parts of DO already so that one shouldn't be very
demanding codewise.
It'd be ideal for things such as locating duplicates where the filename isn't the same and similar.
Basic example of expected usage: locating dupes of dummy.jpg (where it might not have same/similar name):
Name match *
and Size is equal to 2331423 bytes
and md5 is equal to 3159D831CD13B74826CAB8681624B7AE
This would locate files which has the same size, and same content (size is there to speed up search).
The same as the example could probably be achieved if "Duplicate files" panel had the comparison
method "size and md5" (i.e no filename, just size), but having md5 (and possibly crc32) on advanced
search would be more flexible.
The duplicate finder's md5 mode already works like that. It won't consider two files as equal unless their sizes and md5s match, and won't even calculate a file's md5 until at least one other file is found with the same size.
It also has the facility to look for duplicates of specific files, to avoid finding all duplicates when you only care about specific ones.
So I think Opus already provides two ways to do what you need, and much better than manually specifying the md5 or crc as a search parameter.
My example was just that, an example of how it could be used.
Here's the difference.. Say you have 900000 files on a disk (quite a few of them
with the same filesize), you don't know the filename used (there's quite a few variants),
but you do know the size and the md5 of that file.
How would you approach it with the current options?
As I see it, the missing md5 option in advanced search seems to be something which was overlooked, and
probably already would've been present if someone thought of it. it sort of belongs there.
My reasoning is that md5 support is present even as a column, so why not being able to search for it.
Btw, when you mentioned it, the duplicate search for specific files, does that ignore the filename, but compares
only size and md5?
Darn, this was a rather not so obvious find.. searching for a specific file (while having md5 checked), more or less implies
that either it first matches filename then md5, or it wades through everything only considering md5.
It seems to actually do size and md5 (and ignores filename) comparison.
When I tried I copied one of those files to d:\tmp, renamed it to xx.xxx, then did a find specific.. and it found them..fast.
The suggestion still stands though, as that were an example of it's possible usage.
The MD5 mode implies size as if the sizes are different it's a pretty fair bet the files are different, so no need to do the checksum in the first place.
@jon, lol.. DO never ceases to surprise.. Before I searched for md5 sum in advanced search, I thought it already had that.
DO usually has whatever you can think of and more, so that missing, that too was a surprise.
Btw, that it checked size first wasn't the what I were impressed with.. but that in disregarded filename when
doing a specific file search.. that were a surprise.
