https://bugs.kde.org/show_bug.cgi?id=267131
--- Comment #31 from [email protected] --- (In reply to Maik Qualmann from comment #30) > When I read SQLiteBrowser in this context, I feel dizzy. > The update function in the collection settings does exactly what it's > supposed to do. I often use it to test different scenarios or reproduce bugs. > We've already fully enabled the new file UUID for network drives. Not yet > for local hard drives and removable media; there's still a fallback to the > partition UUID. > There are various reasons for this, e.g., support for read-only > media/partitions. A collection that isn't recognized won't be scanned. New > hard drives that haven't been formatted are problematic, as they can contain > the same partition UUID. > Image tags can also be lost with a new setup, e.g., if sidecars are used but > reading from sidecars was forgotten. > > Maik Maybe the update function worked, but the database was already corrupted because "digikam was started and somehow did a scan after an rsync"? All I know is that all tags disappeared and the Refresh icon into a Network DB didn't solve it, and most users would stop there and not know what to do. I guess there are perhaps some use cases for UUID; it just seemed strange for users to be allowed to make that choice without numerous warnings, and incorrect nomenclature, and now it seems most users need to be rescued from this. I'm not quite sure how the internals of digikam work ("file UUID"; is that just a UUID of a file path?) so I can't comment. Though, perhaps if digikam stores its db by default in the collection, it could detect a copied/moved collection by noting its database was moved and no longer matches, and prompting. All I was trying to say was that I notice a Critical problem that will punish 99% of regular users unless it is addressed, (nor mentioned in the docs or config UI or setup wizard?,) and for posterity posted the only way I know that can solve it with a backup (I have found no way to solve this without a backup unless there's a way to rescan the collection). I'll leave further discussion to you all. Cheers. -- You are receiving this mail because: You are watching all bug changes.
