Summary: | Tag view does not always show children | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | kde |
Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 4.14.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.4.0 | |
Sentry Crash Report: |
Description
kde
2016-12-30 11:39:26 UTC
As bug #374327, It's not reproducible here... Please check with current universal AppImage Linux bundle available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier I tried digikam-5.4.0-01-x86-64.appimage When executing it, it complains about not being able to convert to version 8 of the database. (see below). On further investigation, I also seem to be missing many tags that I made in the past. That leads me to believing I'm dealing with a corrupt database, not a bug. I guess the best way ahead would be to close this bug and start with a new digikam database :( Any pointers regarding salvaging my tag database would be appreciated. I put a lot of work into organizing this collection, and I would hate to have to start over. digikam.coredb: Core database: running schema update digikam.geoiface: ---- digikam.coredb: Core database: have a structure version 7 digikam.coredb: Core database: makeUpdates 7 to 8 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IF EXISTS identifier' at line 2" 1064 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ] Statement [ "ALTER TABLE AlbumRoots\n DROP INDEX IF EXISTS identifier;" ] digikam.coredb: Core database: schema update to V 8 failed! digikam.coredb: Core database: cannot process schema initialization I have now version 5.3 running with a fresh database. I think I managed to rescue most of the tags that I had. I cannot reproduce the behaviour I was seeing so I'll close this one. Apologies for the noise. |