Version: (using KDE 4.2.1) OS: Linux Installed from: Unlisted Binary Package 4 days ago Digikam was unable to start. It was telling me that it was unable to upgrade database from version 4 to version 5. I didn't understand and was unable to view logs. Now I've lost my database. Over 5000 .raw files tagged are now untagged :( But I have the ideé that Digikam could make un backup of the database every Week to prevent datalost during crashes. I think it would be reassuring for those who have huge collection with lot of raw files. Users could have the choice of a weekly or a monthly backup and could choose the directories. Well it's just an idea but it would protect me from loosing 3 month of jub. . . PS : sorry if my english is not good. . . french guy inside.
Marcel, "Et voilà" This is the last master of piece of software to do in digiKam before to publish 1.0 version (:=))) We will need to talking about in the future, when 0.11 lead developement with Batch Queue Manager will be done. Gilles
I think comment #1 from Gilles was inadvertendly placed here ;-) Okanda, what does it mean you lost your db? Did you have harddisk failure? Or did digikam crash before? Data loss should not happen because the underlying database keeps a journal and is transaction safe. I dont think digikam should be doing backups because it is simply not running all the time. Data loss can occur anytime. There are dedicated tools better suited for this purpose.
No, I didn't have harddisk failure. I didn't really lost data. But I was unable to start digikam with my database. So, I move it to antoher folder to be able to start digikam. In the collection options tab, I change the directory to where I moved my database to test if Digikam could load it but it didn't. So I lost all my tags (label?) list. And so, all my raw files that were tagged are now untagged (no problem with the jpeg because the tags are in the file). I'm not a programmer but I think it wouldn't be so hard to do this. Digikam simply have to copy the current database.db to database_date.backup once a week.
Hi Okanda, i would imagine that your database is still fine but that you upgraded/installed a new version of digikam which couldn't deal with your old database ("unable to upgrade database from version 4 to version 5."). It happened to me also but mine didn't have much useful info. So the information is still there, but digikam 0.10 can't load it, downgrading digikam would work but it is of course not the best solution. @devels: is there perhaps a simple sql script to rescue the tags from the old DB and load them into the new one?
On the other hand, i strongly second this bug original wish request: having the DB being backed up doesn't mean digikam has to be running permanently, but it can remind/offer you to backup the DB (ie, copy the file on an external media for instance) when quitting the application, or after loading additional 100 or 1000 or XX images, or after a week/month/XX of last backup when you start it again. Of course we should all be running backups anyways, but some data is more critical than other... Actually i would love to be able to export partial databases for backup purposes... exporting all entries/tags/thumbnails/whatever related to all my pictures in the folder /foor/bar1 in a standalone DB1, then i can create a DVD with the whole content of /foo/bar1 and the associated DB1 inside. :-) See also bug #113715 for this one.
I mark this entry as dupplicate of 224312. The topic is the same. Please continue to talk about at this place. Gilles Caulier *** This bug has been marked as a duplicate of bug 224312 ***