[Digikam-devel] [Bug 283502] database upgrade v5 to v6 failed

[Kusi]

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





--- Comment #6 from Kusi <kusi forum titlis org>  2011-10-08 14:00:34 ---
(In reply to comment #5)

> table names are different for the two schemas, so if the same name is given to
> the two it's possible to have one schemas containing the tables for both
> metadata and thumbnails (there is one table with the same name but also have
> same columns)

ah, ok now I understand. I perform a backup of the metadata schema with
mysqldump from time to time, so I prefer not having thumbnails in it there. A
thumbnail schema dump is more than 500mb in my case.

> > 3) On closer look at the error message, I figured out that it was the metadata
> > db, not the thumbdb which was missing the procedure:
> > <<Unable to execute query" "PROCEDURE digikamdb.create_index_if_not_exists does
> > not exist>>
> > So I had a look in dbconfig.xml for the "create_index_if_not_exists" procedure
> > for the main metadata db. Analog to your suggestion, I executed on the metadata
> > db
> 
> it should be the same procedure, but this is the first time we see it missing
> from the metadata db (instead of the thumbnails one), it's good to know

if you need more information from my setup to figure out why that happened let
me know. I already "fixed" once my digikam db directly on mysql-level. I had
some spurious duplicates in the tags table, which wouldn't let me use digikam
properly. Because of my "fix" (please dont call it breakage :), maybe I broke
the condition for a successful schema update.

> 
> well it's workarounded not exactly resolved ;)

...but my workaround should be ok, right? Or do I risk data corruption? True
that this BUG cannot be set to resolved, though.

> it's a difficult bug, it goes deep in all digikam database managment, need many
> lines of code change and some good testing.

Good luck then :) Keep up the great work for digikam!

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