[digiKam-users] Bug? Not all duplicates found.

[digikam-users.johnny1000 at spamgourmet.com]

Thank you Maik for taking the time :o)

Is it a bug then, so I should open a bug report?

I think I understand most of what you explain about QSet, since I know 
sets from Python, and they too are unordered and use hashes for their 
internal logistics.

The difference between GUI and database is a different matter, but it's 
a waste of time to go further into that if the behaviour I see is simply 
a bug :o)

Best regards :o)

Johnny :o)

Den 22.01.2022 kl. 15.44 skrev Maik Qualmann - metzpinguin at gmail.com:
> Well, the result you see in the GUI certainly won't differ. The entries you
> see in the ImageSimilarity table are not the complete end result.
> Why are there different entries in this table? We use a QSet to store the
> image IDs. QSet is unordered and uses a hash to store the information.
> Therefore, the order of the image IDs in the QSet is never the same across
> program starts. This results in the fact that the same images are never always
> compared with one another. This can result in additional entries in the table,
> but they have the same search range. The end result is always the same.
> 
> Maik