|
|
Revising what should be cleaned on database change and found that: 1) /Temp/Thumbs/ are saved per image data hash, so shouldn't be related to DB track ids 2) /Temp/Waveforms/ are per track id and thus might need to be cleaned once the restored database is totally different database (with different track ids) 3) /Temp/Transcoded_Media_Files/ are per track id, but currently are auto-cleaned per settings in Options > Media Sharing > Cache 4) /Temp/Cached_Cloud_Files/ currently aren't track id dependent and are auto cleaned per settings in Options > Player > Streaming > Maximum cache size 5) /Temp/AlbumImages/ 6) /Temp/ImageCache/ So potential candidates to clear once DB is replaced are 2, 3, 5, 6 But this should happen only once the DB is replaced by different DB (with another DB id) So my suggestion is to write last used DB id into persistent.json and once MM finds that the DB differs then it could run background task to clean the cache. But I don't think that this should be done automatically, but rather ask user something like: "MediaMonkey detected that different library database file is used, do you wish to clean cached files for the old database?" [Yes][No] image.png (11,978 bytes) image-2.png (4,473 bytes) |
|
|
Assigned to Rusty for review/wording suggestions. |
- Anonymous
