In a large library, full rebuild of the database will take a long time each time it's re-built.
It would be awesome if there is a way to also store last changed timestamp in the db, and only update the hashes of files changed in the next re-build.
I think this will require a db layer change, so might be difficult.
In a large library, full rebuild of the database will take a long time each time it's re-built.
It would be awesome if there is a way to also store last changed timestamp in the db, and only update the hashes of files changed in the next re-build.
I think this will require a db layer change, so might be difficult.