unwanted clear and rescan after update
Had results of a whole scan on the screen and update database scan started.
Meanwhile looked to see if newer version of bliss available. It was.
Did update but bliss then went directly to a clear and rescan
If this an intended behaviour?
Errol Pillemer commented
don't clear and rescan gets my vote
Nathan Freedenberg commented
don't clear and rescan on every new version get my vote.
Yeah, performing a full rescan (rather than migrating the database) in the case of a change would be a good compromise.
Frank Köhntopp commented
I understand this may be necessary if tag relevant things change between versions, or database definitions change. Maybe updates could do this only if technically necessary...?
Yes, all new versions initiate a clear and rescan.
Shall I change the title to "don't clear and rescan on every new version"?