[KimDaBa] MD5 sums completed.

[Jesper K. Pedersen]

Daniel Berger <daniberger at gmx.ch> writes:

| Jesper K. Pedersen wrote:
| 
| >Daniel Berger <daniberger at gmx.ch> writes:
| >
| >| Jesper K. Pedersen wrote:
| > | | >Due to some coworkers of mine who is into cryptology, the chances of
| > two
| 
| >| >files having the same MD5 sum is in the order of magnitude of 1 to 2^64, so
| >| >I don't think there are any reason to fear that kind of problems ;-)
| >| >
| >| >
| > | | Shure, but what if I've duplicated images in different locations
| > (maybe
| 
| >| even with the same name.)?
| >I'm not sure about that.
| >Why you have that anyway, and is it important that KimDaBa shows both?
| >
| I'm only asking what happes when this occurs. I don't have that or think
| that I need that, I just asked myself,
| 
| because they would have the same md5 sums and what KimDaBa will do then...
When the first is read in, its MD5 will be put into the md5 mapping, and
when the second is read in, KimDaBa will find the previous file from the
mapping, and hmmm and hmmm, well nothing because the other file still
exists, so KimDaBa will simply have both inside it.

If however you move one of the file, then hmm hmm then its likely that
KimDaBa will find the one not moved, which it then will conclude is not
moved, and thus not touch - I guess ;-)

You gotta try to be 100% sure.