[Digikam-devel] [Bug 215486] collection not found in location on disk with uuid (lvm volume)

[simon at margo.student.utwente.nl]

https://bugs.kde.org/show_bug.cgi?id=215486





--- Comment #1 from  <simon margo student utwente nl>  2009-11-20 22:22:00 ---
sorry, mousing error....
continuing here

-------

the collection


(Folder /home/simon/Photos on the volume with the id:<uuid>)

is currently not found on your system
please choose the most appropriate action
A) database is located on temp storage
B) take no action
-----------------

This is wrong on a lot of levels:
- I don't _know_ about my collections, as I have only one
- I've been using this collection for a long time and had several updates (with
similar problems, but never resulting in a total loss of all database
information)
- the actual database is still there, and contains data 
- neither action proposed is or could be appropriate
- the reference to the setup dialog is misleading, since the actual path to the
configuration in digikam is elsewhere.
- the actual database is still there _and_ is the cause of the problem, because
it contains bad information about paths and volume-ids that earlier versions of
digikam have put there themselves.
- I get two of these dialogs, for both entries in the database concerning my
rootpaths or whatever.


I managed to fix it partially, or completely (I'm not sure yet) thanks to some
hints on the ubuntu forum:
http://ubuntuforums.org/showthread.php?t=1192655
(The fix was to remove the rootpaths records in the database using
sqlitebrowser, and letting digikam create a new entry. Then checking what this
looks like and putting that in the old databasefile on each of my rootpath
entries got me a single dialog like above and a working "collection" with my
tags available again (I hope)

and the bug looks somewhat like this one:
https://bugs.kde.org/show_bug.cgi?id=193522

but my situation is different.

In general, I think a lot more care should be taken to deal with this database
around upgrades and in general. I have growing reluctance to trust my photos
and especially the metadata to digikam because of such an upgrade experience. I
have 10s of thousands of images, (I know, way too much, but it takes time to
weed them out). If I put in time to tag them, I want to know my data is safe!

How hard can it be to write a database recovery tool (inside digikam) to handle
this kind of situation. If a used has backups, the data in it should be
recoverable with a small bit of assistance from the user. It should recover
from any "collection" with any version of digikam's database formats. The main
thing is that images retain the links to their tags and ratings and comments,
those things cannot be generated by the machine.

Cheers

Simon

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.