paolobenve
commented
6 years ago We could only recreate them when we detect a change.
I considered that possibility, and dropped it because:
- it's quite difficult to know when date, gps and search albums have to be generated
- the process of generating the album internally has to be performed, because the cached album could be made invalid by the last photo in the album; and anyway the json file datetime must be updated, its datetime is the garantee that it's valid (the json file could be touched without saving it, but I'd prefer to save it anyway, it doesn't make a big difference)
And search index files for album metadata are considered stale and deleted. At the first run, one can search for keywords on album's metadata. On the second run, the same search fails.
Yes, now album.read_album_ini() is executed only if the json file is invalid. Perhaps it could be executed every time, couldn't it?
pmetras
Another strange behaviour with master branch, probably a case for better optimization.
.jsonindex files are created..jsonfiles are generated while there were no changes between the two runs. Better, some stale files are suppressed when there's analbum.inifile!So image files are generated only when changed. But index files are always generated. We could only recreate them when we detect a change.
And search index files for album metadata are considered stale and deleted. At the first run, one can search for keywords on album's metadata. On the second run, the same search fails.