Scan for new items takes ages after syncing collection btw. two computers

[Phil]

On 30/01/17 20:03, Andrew Goodbody wrote:
>
>
> On 30/01/17 16:18, news at tcrass.de wrote:
>> Chris,
>>
>>> It's probably because Unison updates the 'last access' date field on
>>> the files and Digikam uses this to decide whether to resacn.
>>
>>> In Unix/Linux a file has three times associated with it:-
>>>
>>>     Modified time - last time the file contents were changes (write or
>>> append)
>>>     Accessed time - last time the file was accessed (read or write)
>>>     Status changed - last time the attributes (owner, permissions,
>>> etc.) were changed
>>
>> yeah, that's what I came up with, too -- the digikam4.db file will
>> probably have its access time changed during syncing.
>>
>>> Digikam will compare its database with one (or more) of the above file
>>> times I expect.  A Digikam expert will no doubt tell us.
>>
>> But if so, I still wonder where digikam keeps record of digikam4.db's
>> access time?
>
> It doesn't, that's not how it works.
>
> digiKam stores the path to the root of the collection in the database
> and this can look different on different systems, hence it will do a
> full rescan.

Here the db is synced in one case, shared in the other case, so the 
collection root paths are identical on the two machines.
Philip