<div dir="ltr"><div>Thank you very much Maik,</div><div><br></div><div>Now, everything seams ok.</div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Philippe<br><br>e-mail :<span style="font-size:12.8px"> </span><a href="mailto:pdeyres@gmail.com" style="font-size:12.8px" target="_blank">pdeyres@gmail.com</a></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div><br></div></div></blockquote></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mar. 23 août 2022 à 23:20, Maik Qualmann <<a href="mailto:metzpinguin@gmail.com">metzpinguin@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">To delete the column in the SQLiteBrowser you should run this command:<br>
<br>
ALTER TABLE Albums DROP COLUMN modificationDate;<br>
<br>
Maik<br>
<br>
Am Dienstag, 23. August 2022, 15:41:52 CEST schrieb Philippe Deyres:<br>
> Thank you for your help,<br>
> <br>
> What's weird is that I recently migrated from Ubuntu 18.04 to 22.04. And<br>
> therefore from Digikam version 6.xx to version 7.5.<br>
> After migration, the test I performed on Digikam was OK.<br>
> The problem arose after...<br>
> <br>
> I tried to drop the column using sqlitebrowser, but I get an error when<br>
> reintegrating the table:<br>
> <br>
> *root@philippe-ub:/home# sqlitebrowser*<br>
> <br>
> <br>
> <br>
> <br>
> *QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to<br>
> '/tmp/runtime-root'executeSQL: "error in trigger delete_albumroot: no such<br>
> table: main.Albums (ALTER TABLE \"main\".\"sqlb_temp_table_1\" RENAME TO<br>
> \"Albums\")""Erreur lors du changement de nom de la table sqlb_temp_table_1<br>
> vers Albums.\nMessage du moteur de Base de Données :\nerror in trigger<br>
> delete_albumroot: no such table: main.Albums (ALTER TABLE<br>
> \"main\".\"sqlb_temp_table_1\" RENAME TO<br>
> \"Albums\")"root@philippe-ub:/home# *<br>
> <br>
> Philippe<br>
> <br>
> e-mail : <a href="mailto:pdeyres@gmail.com" target="_blank">pdeyres@gmail.com</a><br>
> <br>
> <br>
> Le mar. 23 août 2022 à 12:33, Maik Qualmann <<a href="mailto:metzpinguin@gmail.com" target="_blank">metzpinguin@gmail.com</a>> a<br>
> <br>
> écrit :<br>
> > An error that can actually never occur. Your "Albums" table already has a<br>
> > "modificationDate" column. The cause could be that the update has already<br>
> > been<br>
> > run through, but it was aborted before the database version number was<br>
> > set.<br>
> > Since you are probably using the Ubuntu Snap packages, this may also be<br>
> > the<br>
> > cause. Snap packages use a sandbox and are unusable for use with digiKam.<br>
> > The<br>
> > list of known issues with the Ubuntu digiKam Snap packages is pretty long<br>
> > now.<br>
> > You could open the digiKam4.db with the SQLiteBrowser and delete the<br>
> > "modificationDate" column in the "Albums" table. Backup the digikam4.db<br>
> > should<br>
> > be a matter of course.<br>
> > <br>
> > Maik<br>
> > <br>
> > Am Dienstag, 23. August 2022, 11:46:14 CEST schrieb Philippe Deyres:<br>
> > > Hi everybody,<br>
> > > <br>
> > > I'm running Linux Ubuntu 22.04, with Digikam 7.5<br>
> > > Database is local.<br>
> > > <br>
> > > When i run digikam, i have this message:<br>
> > > *Impossible d'effectuer la mise à jour du schéma de base données*<br>
> > > * de la version 13 vers la version 14philippe@philippe-ub:~$<br>
> > > digikamdigikam.widgets: Use installed iconsdigikam.general: Switch to<br>
> > > widget style: ""digikam.general: AlbumWatch is<br>
> > > <br>
> > > disableddigikam.general: Database Parameters: Type:<br>
> > > "QSQLITE" DB Core Name:<br>
> > > "/home/philippe/Logiciels/digikam/digikam4.db" DB Thumbs Name:<br>
> > > "/home/philippe/Logiciels/digikam/thumbnails-digikam.db" DB<br>
> > > <br>
> > > Face Name:<br>
> > > "/home/philippe/Logiciels/digikam/recognition.db" DB Similarity<br>
> > > Name: "/home/philippe/Logiciels/digikam/similarity.db"<br>
> > > Connect Options: "" Host Name: "" Host<br>
> > > port: -1 Internal Server: false Internal<br>
> > > Server Path: "" Internal Server Admin Cmd: "mysqladmin"<br>
> > > Internal Server Serv Cmd: "" Internal Server Init Cmd: ""<br>
> > > Username: "" Password:<br>
> > > ""digikam.dbengine: Loading SQL code from config file<br>
> > > "/usr/share/digikam/database/dbconfig.xml"digikam.dbengine: Checking<br>
> > > XML version ID => expected: 3 found: 3digikam.coredb: Core<br>
> > > database: running schema updatedigikam.coredb: Core database: have a<br>
> > > structure version 13digikam.coredb: Core database: makeUpdates 13<br>
> > > to 15digikam.dbengine: Failure executing query: "" Error messages:<br>
> > > "Impossible d'exécuter l'instruction" "duplicate column name:<br>
> > > modificationDate" "1" 2 Bound values: ()digikam.dbengine: Error while<br>
> > > executing DBAction [ "UpdateSchemaFromV13ToV14" ] Statement [ "ALTER<br>
> > > TABLE Albums ADD modificationDate DATETIME;" ]digikam.coredb: Core<br>
> > > database: schema update to V 14 failed!digikam.coredb: Core database:<br>
> > > cannot process schema initializationdigikam.general: KMemoryInfo:<br>
> > > Platform identified : "LINUX"digikam.general: KMemoryInfo: TotalRam:<br>
> > > 8311914496digikam.general: Allowing a cache size of 396<br>
> > > MBQThreadStorage: Thread 0x7f98d1ae7860 exited after QThreadStorage 12<br>
> > > destroyedphilippe@philippe-ub:~$ *<br>
> > > <br>
> > > <br>
> > > *I see same problem in a post in 2020.*<br>
> > > <br>
> > > <br>
> > > *Thanks for your help.*<br>
> > > <br>
> > > <br>
> > > Philippe<br>
> > > <br>
> > > e-mail : pdeyres@gmail.c <<a href="mailto:pdeyres@gmail.com" target="_blank">pdeyres@gmail.com</a>>om<br>
<br>
<br>
<br>
<br>
</blockquote></div>