So, I finally collected all the data - I watched the "0 scan" (the last
scan before the change), 1st scan (after the change) and 2nd scan (after
the change)
"0 scan":
(Last scan BEFORE changes)
tracks.timestamp
1624895572 - Montag, 28. Juni 2021 17:52:52 GMT+02:00 DST (ctime?)
tracks.filesize
5898100
tracks.added_time
1643710345 - Dienstag, 1. Februar 2022 11:12:25 GMT+01:00
tracks.updates_time
1643710345 - Dienstag, 1. Februar 2022 11:12:25 GMT+01:00
scanned_files.timestamp
1624895572 - Montag, 28. Juni 2021 17:52:52 GMT+02:00 DST (ctime = mtime
at that point)
scanned_files.filesize
5898100
1st scan (after changes):
tracks.timestamp
1624895572 - Montag, 28. Juni 2021 17:52:52 GMT+02:00 DST (ctime?)
tracks.filesize
5898100
tracks.added_time
1643710345 - Dienstag, 1. Februar 2022 11:12:25 GMT+01:00
tracks.updates_time
1643710345 - Dienstag, 1. Februar 2022 11:12:25 GMT+01:00
scanned_files.timestamp
1644444840 - Mittwoch, 9. Februar 2022 23:14:00 GMT+01:00 (mtime)
scanned_files.filesize
5890048
After this (1st) scan, the track and album had been (on
contributor_track.contributor and contributor_track.album) still be
linked to the OLD contributor ("Nalin & Kane")
2nd scan (after changes):
tracks.timestamp
1644444840 - Mittwoch, 9. Februar 2022 23:14:00 GMT+01:00 (mtime)
tracks.filesize
5890048
tracks.added_time
1643710345 - Dienstag, 1. Februar 2022 11:12:25 GMT+01:00
tracks.updates_time
1644484141 - Donnerstag, 10. Februar 2022 10:09:01 GMT+01:00
scanned_files.timestamp
1644444840 - Mittwoch, 9. Februar 2022 23:14:00 GMT+01:00 (mtime)
scanned_files.filesize
5890048
After this (2nd) scan, the track and album finally had been (on
contributor_track.contributor and contributor_track.album) still be
linked to the NEW contributor ("Nalin + Kane")
As far as I can see, with 1st scan, scanned_files.timestamp and
scanned_files.filesize have been changed, so they were different now
from tracks.timestamp and tracks.filesize.
But this lead to no changes on any "contributor-files".
Only on 2nd scan the comparison scanned_files.timestamp !=
tracks.timestamp (or scanned_files.filesize != tracks.filesize) lead to
changes within the contributor-fields in library.db ...
------------------------------------------------------------------------
frank1969's Profile: http://forums.slimdevices.com/member.php?userid=31156
View this thread: http://forums.slimdevices.com/showthread.php?t=115919
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
