-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Clean database" option randomly nukes some galleries' metadata #635
Comments
Well, I hope you made a backup! 😬 DB cleanup actually makes an automatic backup so your metadata might not be lost -- Search in the LRR folder (openable from the windows app) for an This issue actually doesn't have anything to do with renaming -- I suspect you modified the contents of the archives after adding them to LRR, which leads to their IDs changing. (IDs are calculated based on a hash of the archive file) Modifying files used to simply disconnect them from their database entry, but I made some changes in v.0.7.7 to alleviate this:
The database cleanup routine, on the other end, goes through the recorded IDs in the database and removes them if it can't find a matching file. Since the old ID now technically doesn't match any existing hash (as the archive data itself was modified), it gets removed. There's a warning system in place so you need to run the cleanup twice for it to actively delete old entries, but nevertheless I'll admit there was a fatal flaw here 🙏I'm pushing a change to the cleanup routine so that it'll try to change the ID to the new one before removing data. Thanks for the report! Hopefully this doesn't happen again. 😅 |
LRR Version and OS
v0.8.5
Windows 10 MSI
Bug Details
Clicked the "clean database" button to try and "remove the entries that aren't on my filesystem", but instead it nuked the metadata of some galleries that are ON my filesystem (but just renamed), and also removed them from their respective categories. I thought this only affected the entries that I have renamed, but it also seemed to affect the entries that haven't ever been renamed or moved. Countless hours of work into tagging were lost on one simple click. ┗( T﹏T )┛
Matching Logs
Screenshots
The text was updated successfully, but these errors were encountered: