[digiKam-users] Core database: schema update to V 14 failed!

Philippe Deyres pdeyres at gmail.com
Tue Aug 23 14:41:52 BST 2022


Thank you for your help,

What's weird is that I recently migrated from Ubuntu 18.04 to 22.04. And
therefore from Digikam version 6.xx to version 7.5.
After migration, the test I performed on Digikam was OK.
The problem arose after...

I tried to drop the column using sqlitebrowser, but I get an error when
reintegrating the table:

*root at philippe-ub:/home# sqlitebrowser*




*QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-root'executeSQL:  "error in trigger delete_albumroot: no such
table: main.Albums (ALTER TABLE \"main\".\"sqlb_temp_table_1\" RENAME TO
\"Albums\")""Erreur lors du changement de nom de la table sqlb_temp_table_1
vers Albums.\nMessage du moteur de Base de Données :\nerror in trigger
delete_albumroot: no such table: main.Albums (ALTER TABLE
\"main\".\"sqlb_temp_table_1\" RENAME TO
\"Albums\")"root at philippe-ub:/home# *

Philippe

e-mail : pdeyres at gmail.com


Le mar. 23 août 2022 à 12:33, Maik Qualmann <metzpinguin at gmail.com> a
écrit :

> An error that can actually never occur. Your "Albums" table already has a
> "modificationDate" column. The cause could be that the update has already
> been
> run through, but it was aborted before the database version number was
> set.
> Since you are probably using the Ubuntu Snap packages, this may also be
> the
> cause. Snap packages use a sandbox and are unusable for use with digiKam.
> The
> list of known issues with the Ubuntu digiKam Snap packages is pretty long
> now.
> You could open the digiKam4.db with the SQLiteBrowser and delete the
> "modificationDate" column in the "Albums" table. Backup the digikam4.db
> should
> be a matter of course.
>
> Maik
>
> Am Dienstag, 23. August 2022, 11:46:14 CEST schrieb Philippe Deyres:
> > Hi everybody,
> >
> > I'm running Linux Ubuntu 22.04, with Digikam 7.5
> > Database is local.
> >
> > When i run digikam, i have this message:
> > *Impossible d'effectuer la mise à jour du schéma de base données*
> > * de la version 13 vers la version 14philippe at philippe-ub:~$
> > digikamdigikam.widgets: Use installed iconsdigikam.general: Switch to
> > widget style:  ""digikam.general: AlbumWatch is
> > disableddigikam.general: Database Parameters:   Type:
> >     "QSQLITE"   DB Core Name:
> > "/home/philippe/Logiciels/digikam/digikam4.db"   DB Thumbs Name:
> >      "/home/philippe/Logiciels/digikam/thumbnails-digikam.db"   DB
> > Face Name:
> > "/home/philippe/Logiciels/digikam/recognition.db"   DB Similarity
> > Name:        "/home/philippe/Logiciels/digikam/similarity.db"
> > Connect Options:           ""   Host Name:                 ""   Host
> > port:                 -1   Internal Server:           false   Internal
> > Server Path:      ""   Internal Server Admin Cmd: "mysqladmin"
> > Internal Server Serv Cmd:  ""   Internal Server Init Cmd:  ""
> > Username:                  ""   Password:
> > ""digikam.dbengine: Loading SQL code from config file
> > "/usr/share/digikam/database/dbconfig.xml"digikam.dbengine: Checking
> > XML version ID => expected:  3  found:  3digikam.coredb: Core
> > database: running schema updatedigikam.coredb: Core database: have a
> > structure version  13digikam.coredb: Core database: makeUpdates  13
> > to  15digikam.dbengine: Failure executing query: "" Error messages:
> > "Impossible d'exécuter l'instruction" "duplicate column name:
> > modificationDate" "1" 2 Bound values:  ()digikam.dbengine: Error while
> > executing DBAction [ "UpdateSchemaFromV13ToV14" ] Statement [ "ALTER
> > TABLE Albums ADD modificationDate DATETIME;" ]digikam.coredb: Core
> > database: schema update to V 14 failed!digikam.coredb: Core database:
> > cannot process schema initializationdigikam.general: KMemoryInfo:
> > Platform identified :  "LINUX"digikam.general: KMemoryInfo: TotalRam:
> > 8311914496digikam.general: Allowing a cache size of 396
> > MBQThreadStorage: Thread 0x7f98d1ae7860 exited after QThreadStorage 12
> > destroyedphilippe at philippe-ub:~$ *
> >
> >
> > *I see same problem in a post in 2020.*
> >
> >
> > *Thanks for your help.*
> >
> >
> > Philippe
> >
> > e-mail : pdeyres at gmail.c <pdeyres at gmail.com>om
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220823/1697622e/attachment.htm>


More information about the Digikam-users mailing list