Re: Dates missing from my digiKam database
"Randolph M. Fritz" <[email protected]> Fri, 24 Jul 2026 12:00:47 -0700
| Newsgroups | gmane.comp.kde.digikam.user |
|---|---|
| Message-ID | <CANeAMo+XQmhZ8CS_uF0q1_C4e=QOw2bw-X2VFToiBBXdx8z2tw@mail.gmail.com> |
--0000000000003d456106575ffe84 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ah. Good idea. I tried this in a different account, since I do have multiple accounts for different tasks, and I got the "Could not start database initializer" error again. I switched to SQLite and it worked, starting and properly showing dates. Which, unfortunately, does not help the problem with my main database. I will, I guess, await a resolution of the MariaDB issue. --=20 Randolph M. Fritz || [email protected] On Fri, Jul 24, 2026 at 10:22=E2=80=AFAM Maik Qualmann <[email protected]= om> wrote: > This is currently a MariaDB issue; it affects openSUSE Tumbleweed as well= . > That=E2=80=99s simply the downside of using cutting-edge software sometim= es. > > Maik > > Am Freitag, 24. Juli 2026, 15:53:43 Mitteleurop=C3=A4ische Sommerzeit sch= rieb > Gilles Caulier: > > Create a new account on your system and run from scratch digiKAm on a > > small collection. > > > > Gilles Caulier > > > > Le ven. 24 juil. 2026 =C3=A0 15:50, Randolph M. Fritz <[email protected]= om> a > =C3=A9crit : > > > I just tried creating a new database on a small set of images, and I > was > > > asked if I wanted to delete digikamrc. No! I don't! I don't want to > throw > > > away my existing database of, literally, decades of images. > > > > > > How do I run this test without losing all my data? > > > -- > > > Randolph M. Fritz || [email protected] > > > > > > On Thu, Jul 23, 2026 at 12:03=E2=80=AFPM Randolph M. Fritz <rmfritz3@= gmail.com> > > wrote: > > >> Tried this with 9.2.0; same error, fell back to 9.1.0 again. > > >> > > >> I'm just relieved I didn't have to roll my database all the way back= . > > >> -- > > >> Randolph M. Fritz || [email protected] > > >> > > >> On Mon, Jul 20, 2026 at 9:56=E2=80=AFPM Randolph M. Fritz <rmfritz3@= gmail.com> > > wrote: > > >>> No, I just tried 9.2.0. I fell back to 9.1.0. I have now attempted = to > > >>> create a new database on a small collection, and the attempt drew t= he > > >>> following error: (I have a screenshot, too, but it's too big for th= e > > >>> mailing list)>>> > > >>>> An error occurred during the internal server start. > > >>>> Details: > > >>>> Could not start database initializer. > > >>>> Executable: /Applications/digiKam.org/ > digikam.app/Contents/lib/mariadb/ > > >>>> bin/mariadb-install-db > > >>>> Arguments: --defaults-file=3D/Applications/digiKam.org/digikam.app= / > > >>>> Contents/Resources/digikam/database/mysql-global.conf, --basedir= =3D/ > > >>>> Applications/digiKam.org/digikam.app/Contents/lib/mariadb/, > > >>>> --datadir=3D/ Users/randolph/Documents/dktest/.mysql.digikam/db_da= ta > > >>>> Process error: Unknown error > > >>>> Please check the database settings in this dialog. > > >>> > > >>> A bit of poking at the command line suggests a missing symlink in t= he > > >>> application bundle, but I really don't know for certain. -- > > >>> Randolph M. Fritz || [email protected] > > >>> > > >>> On Fri, Jul 17, 2026 at 11:27=E2=80=AFPM Gilles Caulier > <[email protected]> wrote: > > >>>> How did you double check that. Did you start a new database from > > >>>> scratch on a small collection to see if the datetime field is > > >>>> populated ? > > >>>> > > >>>> Best regards > > >>>> > > >>>> Gilles Caulier > > >>>> > > >>>> Le sam. 18 juil. 2026 =C3=A0 06:29, Randolph M. Fritz < > [email protected]> a > =C3=A9crit : > > >>>> > Unfortunately, no, that version does not fix the problem. > > >>>> > -- > > >>>> > Randolph M. Fritz || [email protected] > > >>>> > > > >>>> > On Thu, Jul 16, 2026 at 9:37=E2=80=AFPM Maik Qualmann < > [email protected]> > wrote: > > >>>> >> The issue with the date view should be fixed in the digiKam-9.2= .0 > > >>>> >> pre-release; please test it here: > > >>>> >> > > >>>> >> https://files.kde.org/digikam/ > > >>>> >> > > >>>> >> Maik > > >>>> >> > > >>>> >> Am Freitag, 17. Juli 2026, 06:03:22 Mitteleurop=C3=A4ische Somm= erzeit > > >>>> >> schrieb > > >>>> >> > > >>>> >> Randolph M. Fritz: > > >>>> >> > I should add at this point that I can see dates in the file > > >>>> >> > properties, so > > >>>> >> > they're in the image metadata. > > >>>> >> > > > >>>> >> > > I tried creating a small collection like you suggested and > did > > >>>> >> > > the > > >>>> >> > > metadata scan, and it doesn't seem to do anything. Still no > > >>>> >> > > dates in the > > >>>> >> > > display. > > >>>> >> > > > > >>>> >> > > How do I query the internal mysql database? I'm suspecting = at > > >>>> >> > > this point > > >>>> >> > > that the dates are actually in the database, but not being > > >>>> >> > > displayed; can > > >>>> >> > > you send me some commands to run? > > >>>> >> > > -- > > >>>> >> > > Randolph M. Fritz || [email protected] > > >>>> >> > > > > >>>> >> > > > > >>>> >> > > On Thu, Jul 16, 2026 at 1:52=E2=80=AFAM Gilles Caulier > > >>>> >> > > <[email protected]> > > >>>> >> > > > > >>>> >> > > wrote: > > >>>> >> > >> In fact this depend of multiple parameters. > > >>>> >> > >> > > >>>> >> > >> What I don't understand is why the data is not populated i= n > the > > >>>> >> > >> database. If date of shoot cannot be taken from the file > > >>>> >> > >> metadata > > >>>> >> > >> there is a fail back to the file system date. So typically > the > > >>>> >> > >> date > > >>>> >> > >> must be populated in all cases in the database. > > >>>> >> > >> > > >>>> >> > >> I recommend creating a small collection for testing and to > > >>>> >> > >> populate a > > >>>> >> > >> small database with it. You must reproduce the problem. If > yes, > > >>>> >> > >> capture the debug trace from a terminal to see where the > > >>>> >> > >> problem is. > > >>>> >> > >> Look instructions here : > > >>>> >> > >> > > >>>> >> > >> > https://www.digikam.org/contribute/#freezes-and-other-run-time-> >>>> >> > > >> issues > > >>>> >> > >> > > >>>> >> > >> Best regards > > >>>> >> > >> > > >>>> >> > >> Gilles Caulier > > >>>> >> > >> > > >>>> >> > >> Le jeu. 16 juil. 2026 =C3=A0 03:31, Randolph M. Fritz > > >>>> >> > >> <[email protected]> a > > >>>> >> > >> > > >>>> >> > >> =C3=A9crit : > > >>>> >> > >> > I've got the "Write to item and XMP Sidecar" setting > turned > > >>>> >> > >> > on=E2=80=94is that > > >>>> >> > >> > > >>>> >> > >> OK? > > >>>> >> > >> > > >>>> >> > >> > Dates don't seem to be mentioned in the Advanced Metadat= a > > >>>> >> > >> > panel; do I > > >>>> >> > >> > > >>>> >> > >> need to add them? > > >>>> >> > >> > > >>>> >> > >> > -- > > >>>> >> > >> > Randolph M. Fritz || [email protected] > > >>>> >> > >> > > > >>>> >> > >> > > > >>>> >> > >> > On Wed, Jul 15, 2026 at 11:16=E2=80=AFAM Gilles Caulier = < > > >>>> >> > >> > > >>>> >> > >> [email protected]> wrote: > > >>>> >> > >> >> Yes the metadata sync to repopulate the date in the > > >>>> >> > >> >> database. > > >>>> >> > >> >> > > >>>> >> > >> >> But the most important point is to know where to take t= he > > >>>> >> > >> >> date in > > >>>> >> > >> >> metadata in your case. There is a advanced metadata > panel in > > >>>> >> > >> >> digiKam > > >>>> >> > >> >> where you can customize that. Another point is to know = if > > >>>> >> > >> >> the XMP > > >>>> >> > >> >> sidecar option need to be turned on. > > >>>> >> > >> >> > > >>>> >> > >> >> Best regards > > >>>> >> > >> >> > > >>>> >> > >> >> Gilles Caulier > > >>>> >> > >> >> > > >>>> >> > >> >> Le mer. 15 juil. 2026 =C3=A0 17:46, Randolph M. Fritz > > >>>> >> > >> >> <[email protected]> > > >>>> >> > >> > > >>>> >> > >> a =C3=A9crit : > > >>>> >> > >> >> > Thanks. I've been using mySQL internal which, at leas= t > on > > >>>> >> > >> >> > the Mac, > > >>>> >> > >> > > >>>> >> > >> is in fact Maria. > > >>>> >> > >> > > >>>> >> > >> >> > Which option of the maintenance tool should I use? Th= e > > >>>> >> > >> >> > metadata > > >>>> >> > >> > > >>>> >> > >> synchronizer? Or some other option? > > >>>> >> > >> > > >>>> >> > >> >> > -- > > >>>> >> > >> >> > Randolph M. Fritz || [email protected] > > >>>> >> > >> >> > > > >>>> >> > >> >> > On Wed, Jul 15, 2026, 4:51=E2=80=AFAM Gilles Caulier = < > > >>>> >> > >> > > >>>> >> > >> [email protected]> wrote: > > >>>> >> > >> >> >> Migrating the databases without dates will not solve > the > > >>>> >> > >> >> >> problem. > > >>>> >> > >> > > >>>> >> > >> The > > >>>> >> > >> > > >>>> >> > >> >> >> items are not re-scanned. > > >>>> >> > >> >> >> > > >>>> >> > >> >> >> Try to run the maintenance tool and be forced to sca= n > all > > >>>> >> > >> >> >> items. > > >>>> >> > >> >> >> > > >>>> >> > >> >> >> Note: MySQL has diverged from MariaDB in terms of > > >>>> >> > >> >> >> compatibility, > > >>>> >> > >> >> >> particularly with the latest versions of MySQL. We > > >>>> >> > >> >> >> strongly > > >>>> >> > >> > > >>>> >> > >> recommend > > >>>> >> > >> > > >>>> >> > >> >> >> using MariaDB instead of MySQL. > > >>>> >> > >> >> >> > > >>>> >> > >> >> >> Best regards > > >>>> >> > >> >> >> > > >>>> >> > >> >> >> Gilles Caulier > > >>>> >> > >> >> >> > > >>>> >> > >> >> >> Le mer. 15 juil. 2026 =C3=A0 07:20, Randolph M. Frit= z < > > >>>> >> > >> > > >>>> >> > >> [email protected]> a =C3=A9crit : > > >>>> >> > >> >> >> > Since no-one replied, I ran the migration > and=E2=80=A6nothing > > >>>> >> > >> >> >> > happened. > > >>>> >> > >> > > >>>> >> > >> It didn't change the database in settings, and the dates > didn't > > >>>> >> > >> reappear. > > >>>> >> > >> Do I have to rebuild the database from scratch? How do I > even > > >>>> >> > >> do that? > > >>>> >> > >> > > >>>> >> > >> >> >> > -- > > >>>> >> > >> >> >> > Randolph M. Fritz || [email protected] > > >>>> >> > >> >> >> > > > >>>> >> > >> >> >> > > > >>>> >> > >> >> >> > On Sun, Jul 12, 2026 at 8:38=E2=80=AFPM Randolph M= . Fritz < > > >>>> >> > >> > > >>>> >> > >> [email protected]> wrote: > > >>>> >> > >> >> >> >> Or at least, the dates don=E2=80=99t show up in t= he =E2=80=9CDates=E2=80=9D > > >>>> >> > >> >> >> >> view. > > >>>> >> > >> >> >> >> > > >>>> >> > >> >> >> >> It=E2=80=99s an internal mySQL database. Is there= any easy > way > > >>>> >> > >> >> >> >> to repair > > >>>> >> > >> > > >>>> >> > >> this? Or would it be better just to migrate to SQLite? (I > have > > >>>> >> > >> 653 GB of > > >>>> >> > >> image files.) > > >>>> >> > >> > > >>>> >> > >> >> >> >>> digiKam: 9.1.0 > > >>>> >> > >> >> >> >>> KDE Frameworks: 6.26.0 > > >>>> >> > >> >> >> >>> Qt: Using 6.11.0 and built against 6.11.0 > > >>>> >> > >> >> >> >>> macOS Sequoia (15.7.7) > > >>>> >> > >> >> >> >>> Build ABI: arm64-little_endian-lp64 > > >>>> >> > >> >> >> >>> Kernel: darwin 24.6.0 > > >>>> >> > >> >> >> >> > > >>>> >> > >> >> >> >> -- > > >>>> >> > >> >> >> >> Randolph M. Fritz || [email protected] > > > > > --0000000000003d456106575ffe84 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Ah. Good idea. I tried this in a different account, s= ince I do have multiple accounts for different tasks, and I got the "C= ould not start database initializer" error again. I switched to SQLite= and it worked, starting and properly showing dates. Which, unfortunately, = does not help the problem with my main database.</div><div><br></div><div>I= will, I guess, await a resolution=C2=A0of the MariaDB issue.</div><div><di= v dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature">= <div dir=3D"ltr"><div>-- <br>Randolph M. Fritz=C2=A0<span>|| </span><a href= =3D"mailto:[email protected]" target=3D"_blank">[email protected]</a></di= v></div></div></div><br></div><br><div class=3D"gmail_quote"><div dir=3D"lt= r" class=3D"gmail_attr">On Fri, Jul 24, 2026 at 10:22=E2=80=AFAM Maik Qualm= ann <<a href=3D"mailto:[email protected]" target=3D"_blank">metzping= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty= le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi= ng-left:1ex">This is currently a MariaDB issue; it affects openSUSE Tumblew= eed as well. <br> That=E2=80=99s simply the downside of using cutting-edge software sometimes= .<br> <br> Maik<br> <br> Am Freitag, 24. Juli 2026, 15:53:43 Mitteleurop=C3=A4ische Sommerzeit schri= eb <br> Gilles Caulier:<br> > Create a new account on your system and run from scratch digiKAm on a<= br> > small collection.<br> > <br> > Gilles Caulier<br> > <br> > Le ven. 24 juil. 2026 =C3=A0 15:50, Randolph M. Fritz <<a href=3D"m= ailto:[email protected]" target=3D"_blank">[email protected]</a>> a <b= r> =C3=A9crit :<br> > > I just tried creating a new database on a small set of images, an= d I was<br> > > asked if I wanted to delete digikamrc. No! I don't! I don'= ;t want to throw<br> > > away my existing database of, literally, decades of images.<br> > > <br> > > How do I run this test without losing all my data?<br> > > --<br> > > Randolph M. Fritz || <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> > > <br> > > On Thu, Jul 23, 2026 at 12:03=E2=80=AFPM Randolph M. Fritz <<a= href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a= >> <br> wrote:<br> > >> Tried this with 9.2.0; same error, fell back to 9.1.0 again.<= br> > >> <br> > >> I'm just relieved I didn't have to roll my database a= ll the way back.<br> > >> --<br> > >> Randolph M. Fritz || <a href=3D"mailto:[email protected]" ta= rget=3D"_blank">[email protected]</a><br> > >> <br> > >> On Mon, Jul 20, 2026 at 9:56=E2=80=AFPM Randolph M. Fritz <= ;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]= </a>> <br> wrote:<br> > >>> No, I just tried 9.2.0. I fell back to 9.1.0. I have now = attempted to<br> > >>> create a new database on a small collection, and the atte= mpt drew the<br> > >>> following error: (I have a screenshot, too, but it's = too big for the<br> > >>> mailing list)>>> <br> > >>>> An error occurred during the internal server start.<b= r> > >>>> Details:<br> > >>>> Could not start database initializer.<br> > >>>> Executable: /Applications/digiKam.org/<a href=3D"http= ://digikam.app/Contents/lib/mariadb/" rel=3D"noreferrer" target=3D"_blank">= digikam.app/Contents/lib/mariadb/</a><br> > >>>> bin/mariadb-install-db<br> > >>>> Arguments: --defaults-file=3D/Applications/digiKam.or= g/<a href=3D"http://digikam.app/" rel=3D"noreferrer" target=3D"_blank">digi= kam.app/</a><br> > >>>> Contents/Resources/digikam/database/mysql-global.conf= , --basedir=3D/<br> > >>>> Applications/digiKam.org/<a href=3D"http://digikam.ap= p/Contents/lib/mariadb/" rel=3D"noreferrer" target=3D"_blank">digikam.app/C= ontents/lib/mariadb/</a>,<br> > >>>> --datadir=3D/ Users/randolph/Documents/dktest/.mysql.= digikam/db_data<br> > >>>> Process error: Unknown error<br> > >>>> Please check the database settings in this dialog.<br= > > >>> <br> > >>> A bit of poking at the command line suggests a missing sy= mlink in the<br> > >>> application bundle, but I really don't know for certa= in. --<br> > >>> Randolph M. Fritz || <a href=3D"mailto:[email protected]= " target=3D"_blank">[email protected]</a><br> > >>> <br> > >>> On Fri, Jul 17, 2026 at 11:27=E2=80=AFPM Gilles Caulier <= br> <<a href=3D"mailto:[email protected]" target=3D"_blank">caulier.g= [email protected]</a>> wrote:<br> > >>>> How did you double check that. Did you start a new da= tabase from<br> > >>>> scratch on a small collection to see if the datetime = field is<br> > >>>> populated ?<br> > >>>> <br> > >>>> Best regards<br> > >>>> <br> > >>>> Gilles Caulier<br> > >>>> <br> > >>>> Le sam. 18 juil. 2026 =C3=A0 06:29, Randolph M. Fritz= <<a href=3D"mailto:[email protected]" target=3D"_blank">rmfritz3@gmail= .com</a>> a <br> =C3=A9crit :<br> > >>>> > Unfortunately, no, that version does not fix the= problem.<br> > >>>> > --<br> > >>>> > Randolph M. Fritz || <a href=3D"mailto:rmfritz3@= gmail.com" target=3D"_blank">[email protected]</a><br> > >>>> > <br> > >>>> > On Thu, Jul 16, 2026 at 9:37=E2=80=AFPM Maik Qua= lmann <<a href=3D"mailto:[email protected]" target=3D"_blank">metzpi= [email protected]</a>> <br> wrote:<br> > >>>> >> The issue with the date view should be fixed= in the digiKam-9.2.0<br> > >>>> >> pre-release; please test it here:<br> > >>>> >> <br> > >>>> >> <a href=3D"https://files.kde.org/digikam/" r= el=3D"noreferrer" target=3D"_blank">https://files.kde.org/digikam/</a><br> > >>>> >> <br> > >>>> >> Maik<br> > >>>> >> <br> > >>>> >> Am Freitag, 17. Juli 2026, 06:03:22 Mitteleu= rop=C3=A4ische Sommerzeit<br> > >>>> >> schrieb<br> > >>>> >> <br> > >>>> >> Randolph M. Fritz:<br> > >>>> >> > I should add at this point that I can s= ee dates in the file<br> > >>>> >> > properties, so<br> > >>>> >> > they're in the image metadata.<br> > >>>> >> > <br> > >>>> >> > > I tried creating a small collectio= n like you suggested and did<br> > >>>> >> > > the<br> > >>>> >> > > metadata scan, and it doesn't = seem to do anything. Still no<br> > >>>> >> > > dates in the<br> > >>>> >> > > display.<br> > >>>> >> > > <br> > >>>> >> > > How do I query the internal mysql = database? I'm suspecting at<br> > >>>> >> > > this point<br> > >>>> >> > > that the dates are actually in the= database, but not being<br> > >>>> >> > > displayed; can<br> > >>>> >> > > you send me some commands to run?<= br> > >>>> >> > > --<br> > >>>> >> > > Randolph M. Fritz || <a href=3D"ma= ilto:[email protected]" target=3D"_blank">[email protected]</a><br> > >>>> >> > > <br> > >>>> >> > > <br> > >>>> >> > > On Thu, Jul 16, 2026 at 1:52=E2=80= =AFAM Gilles Caulier<br> > >>>> >> > > <<a href=3D"mailto:caulier.gill= [email protected]" target=3D"_blank">[email protected]</a>><br> > >>>> >> > > <br> > >>>> >> > > wrote:<br> > >>>> >> > >> In fact this depend of multipl= e parameters.<br> > >>>> >> > >> <br> > >>>> >> > >> What I don't understand is= why the data is not populated in the<br> > >>>> >> > >> database. If date of shoot can= not be taken from the file<br> > >>>> >> > >> metadata<br> > >>>> >> > >> there is a fail back to the fi= le system date. So typically the<br> > >>>> >> > >> date<br> > >>>> >> > >> must be populated in all cases= in the database.<br> > >>>> >> > >> <br> > >>>> >> > >> I recommend creating a small c= ollection for testing and to<br> > >>>> >> > >> populate a<br> > >>>> >> > >> small database with it. You mu= st reproduce the problem. If yes,<br> > >>>> >> > >> capture the debug trace from a= terminal to see where the<br> > >>>> >> > >> problem is.<br> > >>>> >> > >> Look instructions here :<br> > >>>> >> > >> <br> > >>>> >> > >> <a href=3D"https://www.digikam= .org/contribute/#freezes-and-other-run-time-" rel=3D"noreferrer" target=3D"= _blank">https://www.digikam.org/contribute/#freezes-and-other-run-time-</a>= > >>>> >> > >> issues<br> > >>>> >> > >> <br> > >>>> >> > >> Best regards<br> > >>>> >> > >> <br> > >>>> >> > >> Gilles Caulier<br> > >>>> >> > >> <br> > >>>> >> > >> Le jeu. 16 juil. 2026 =C3=A0 0= 3:31, Randolph M. Fritz<br> > >>>> >> > >> <<a href=3D"mailto:rmfritz3= @gmail.com" target=3D"_blank">[email protected]</a>> a<br> > >>>> >> > >> <br> > >>>> >> > >> =C3=A9crit :<br> > >>>> >> > >> > I've got the "Wr= ite to item and XMP Sidecar" setting turned<br> > >>>> >> > >> > on=E2=80=94is that<br> > >>>> >> > >> <br> > >>>> >> > >> OK?<br> > >>>> >> > >> <br> > >>>> >> > >> > Dates don't seem to b= e mentioned in the Advanced Metadata<br> > >>>> >> > >> > panel; do I<br> > >>>> >> > >> <br> > >>>> >> > >> need to add them?<br> > >>>> >> > >> <br> > >>>> >> > >> > --<br> > >>>> >> > >> > Randolph M. Fritz || <a h= ref=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><= br> > >>>> >> > >> > <br> > >>>> >> > >> > <br> > >>>> >> > >> > On Wed, Jul 15, 2026 at 1= 1:16=E2=80=AFAM Gilles Caulier <<br> > >>>> >> > >> <br> > >>>> >> > >> <a href=3D"mailto:caulier.gill= [email protected]" target=3D"_blank">[email protected]</a>> wrote:<br> > >>>> >> > >> >> Yes the metadata sync= to repopulate the date in the<br> > >>>> >> > >> >> database.<br> > >>>> >> > >> >> <br> > >>>> >> > >> >> But the most importan= t point is to know where to take the<br> > >>>> >> > >> >> date in<br> > >>>> >> > >> >> metadata in your case= . There is a advanced metadata panel in<br> > >>>> >> > >> >> digiKam<br> > >>>> >> > >> >> where you can customi= ze that. Another point is to know if<br> > >>>> >> > >> >> the XMP<br> > >>>> >> > >> >> sidecar option need t= o be turned on.<br> > >>>> >> > >> >> <br> > >>>> >> > >> >> Best regards<br> > >>>> >> > >> >> <br> > >>>> >> > >> >> Gilles Caulier<br> > >>>> >> > >> >> <br> > >>>> >> > >> >> Le mer. 15 juil. 2026= =C3=A0 17:46, Randolph M. Fritz<br> > >>>> >> > >> >> <<a href=3D"mailto= :[email protected]" target=3D"_blank">[email protected]</a>><br> > >>>> >> > >> <br> > >>>> >> > >> a =C3=A9crit :<br> > >>>> >> > >> >> > Thanks. I've= been using mySQL internal which, at least on<br> > >>>> >> > >> >> > the Mac,<br> > >>>> >> > >> <br> > >>>> >> > >> is in fact Maria.<br> > >>>> >> > >> <br> > >>>> >> > >> >> > Which option of = the maintenance tool should I use? The<br> > >>>> >> > >> >> > metadata<br> > >>>> >> > >> <br> > >>>> >> > >> synchronizer? Or some other op= tion?<br> > >>>> >> > >> <br> > >>>> >> > >> >> > --<br> > >>>> >> > >> >> > Randolph M. Frit= z || <a href=3D"mailto:[email protected]" target=3D"_blank">rmfritz3@gmail= .com</a><br> > >>>> >> > >> >> > <br> > >>>> >> > >> >> > On Wed, Jul 15, = 2026, 4:51=E2=80=AFAM Gilles Caulier <<br> > >>>> >> > >> <br> > >>>> >> > >> <a href=3D"mailto:caulier.gill= [email protected]" target=3D"_blank">[email protected]</a>> wrote:<br> > >>>> >> > >> >> >> Migrating th= e databases without dates will not solve the<br> > >>>> >> > >> >> >> problem.<br> > >>>> >> > >> <br> > >>>> >> > >> The<br> > >>>> >> > >> <br> > >>>> >> > >> >> >> items are no= t re-scanned.<br> > >>>> >> > >> >> >> <br> > >>>> >> > >> >> >> Try to run t= he maintenance tool and be forced to scan all<br> > >>>> >> > >> >> >> items.<br> > >>>> >> > >> >> >> <br> > >>>> >> > >> >> >> Note: MySQL = has diverged from MariaDB in terms of<br> > >>>> >> > >> >> >> compatibilit= y,<br> > >>>> >> > >> >> >> particularly= with the latest versions of MySQL. We<br> > >>>> >> > >> >> >> strongly<br> > >>>> >> > >> <br> > >>>> >> > >> recommend<br> > >>>> >> > >> <br> > >>>> >> > >> >> >> using MariaD= B instead of MySQL.<br> > >>>> >> > >> >> >> <br> > >>>> >> > >> >> >> Best regards= <br> > >>>> >> > >> >> >> <br> > >>>> >> > >> >> >> Gilles Cauli= er<br> > >>>> >> > >> >> >> <br> > >>>> >> > >> >> >> Le mer. 15 j= uil. 2026 =C3=A0 07:20, Randolph M. Fritz <<br> > >>>> >> > >> <br> > >>>> >> > >> <a href=3D"mailto:rmfritz3@gma= il.com" target=3D"_blank">[email protected]</a>> a =C3=A9crit :<br> > >>>> >> > >> >> >> > Since n= o-one replied, I ran the migration and=E2=80=A6nothing<br> > >>>> >> > >> >> >> > happene= d.<br> > >>>> >> > >> <br> > >>>> >> > >> It didn't change the datab= ase in settings, and the dates didn't<br> > >>>> >> > >> reappear.<br> > >>>> >> > >> Do I have to rebuild the datab= ase from scratch? How do I even<br> > >>>> >> > >> do that?<br> > >>>> >> > >> <br> > >>>> >> > >> >> >> > --<br> > >>>> >> > >> >> >> > Randolp= h M. Fritz || <a href=3D"mailto:[email protected]" target=3D"_blank">rmfri= [email protected]</a><br> > >>>> >> > >> >> >> > <br> > >>>> >> > >> >> >> > <br> > >>>> >> > >> >> >> > On Sun,= Jul 12, 2026 at 8:38=E2=80=AFPM Randolph M. Fritz <<br> > >>>> >> > >> <br> > >>>> >> > >> <a href=3D"mailto:rmfritz3@gma= il.com" target=3D"_blank">[email protected]</a>> wrote:<br> > >>>> >> > >> >> >> >> Or = at least, the dates don=E2=80=99t show up in the =E2=80=9CDates=E2=80=9D<br= > > >>>> >> > >> >> >> >> vie= w.<br> > >>>> >> > >> >> >> >> <br= > > >>>> >> > >> >> >> >> It= =E2=80=99s an internal mySQL database. Is there any easy way<br> > >>>> >> > >> >> >> >> to = repair<br> > >>>> >> > >> <br> > >>>> >> > >> this? Or would it be better ju= st to migrate to SQLite? (I have<br> > >>>> >> > >> 653 GB of<br> > >>>> >> > >> image files.)<br> > >>>> >> > >> <br> > >>>> >> > >> >> >> >>>= digiKam: 9.1.0<br> > >>>> >> > >> >> >> >>>= KDE Frameworks: 6.26.0<br> > >>>> >> > >> >> >> >>>= Qt: Using 6.11.0 and built against 6.11.0<br> > >>>> >> > >> >> >> >>>= macOS Sequoia (15.7.7)<br> > >>>> >> > >> >> >> >>>= Build ABI: arm64-little_endian-lp64<br> > >>>> >> > >> >> >> >>>= Kernel: darwin 24.6.0<br> > >>>> >> > >> >> >> >> <br= > > >>>> >> > >> >> >> >> --<= br> > >>>> >> > >> >> >> >> Ran= dolph M. Fritz || <a href=3D"mailto:[email protected]" target=3D"_blank">r= [email protected]</a><br> <br> <br> <br> <br> </blockquote></div> --0000000000003d456106575ffe84--