Re: Dates missing from my digiKam database
"Randolph M. Fritz" <[email protected]> Fri, 17 Jul 2026 21:28:16 -0700
| Newsgroups | gmane.comp.kde.digikam.user |
|---|---|
| Message-ID | <CANeAMoK3iJL-8g-ku8gDD6roY=6w-xZR=y2++RxqducMJyQr1w@mail.gmail.com> |
--000000000000c9bb340656db1abb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Unfortunately, no, that version does not fix the problem. --=20 Randolph M. Fritz || [email protected] On Thu, Jul 16, 2026 at 9:37=E2=80=AFPM Maik Qualmann <[email protected]= m> 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 Sommerzeit sch= rieb > 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 in 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-issue= s > > >> > > >> Best regards > > >> > > >> Gilles Caulier > > >> > > >> Le jeu. 16 juil. 2026 =C3=A0 03:31, Randolph M. Fritz <rmfritz3@gmai= l.com> > 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 Metadata panel; d= o > 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 the 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 least on the > Mac, > > >> > > >> is in fact Maria. > > >> > > >> >> > Which option of the maintenance tool should I use? The 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 scan all item= s. > > >> >> >> > > >> >> >> Note: MySQL has diverged from MariaDB in terms of compatibilit= y, > > >> >> >> 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. Fritz < > > >> > > >> [email protected]> a =C3=A9crit : > > >> >> >> > Since no-one replied, I ran the migration and=E2=80=A6nothin= g > 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 tha= t? > > >> > > >> >> >> > -- > > >> >> >> > 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 the =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 G= B > 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] > > > > > --000000000000c9bb340656db1abb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Unfortunately, no, that version does not fix the=C2= =A0problem.</div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smart= mail=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></div></div></div></div><br></div><br><div class=3D"g= mail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On = Thu, Jul 16, 2026 at 9:37=E2=80=AFPM Maik Qualmann <<a href=3D"mailto:me= [email protected]">[email protected]</a>> wrote:<br></div><blockqu= ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px= solid rgb(204,204,204);padding-left:1ex">The issue with the date view shou= ld be fixed in the digiKam-9.2.0 pre-release; <br> please test it here:<br> <br> <a href=3D"https://files.kde.org/digikam/" rel=3D"noreferrer" target=3D"_bl= ank">https://files.kde.org/digikam/</a><br> <br> Maik<br> <br> Am Freitag, 17. Juli 2026, 06:03:22 Mitteleurop=C3=A4ische Sommerzeit schri= eb <br> Randolph M. Fritz:<br> > I should add at this point that I can see dates in the file properties= , so<br> > they're in the image metadata.<br> > <br> > > I tried creating a small collection like you suggested and did th= e<br> > > metadata scan, and it doesn't seem to do anything. Still no d= ates in the<br> > > display.<br> > > <br> > > How do I query the internal mysql database? I'm suspecting at= this point<br> > > that the dates are actually in the database, but not being displa= yed; can<br> > > you send me some commands to run?<br> > > --<br> > > Randolph M. Fritz || <a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a><br> > > <br> > > <br> > > On Thu, Jul 16, 2026 at 1:52=E2=80=AFAM Gilles Caulier <<a hre= f=3D"mailto:[email protected]" target=3D"_blank">caulier.gilles@gmai= l.com</a>><br> > > <br> > > wrote:<br> > >> In fact this depend of multiple parameters.<br> > >> <br> > >> What I don't understand is why the data is not populated = in the<br> > >> database. If date of shoot cannot be taken from the file meta= data<br> > >> there is a fail back to the file system date. So typically th= e date<br> > >> must be populated in all cases in the database.<br> > >> <br> > >> I recommend creating a small collection for testing and to po= pulate a<br> > >> small database with it. You must reproduce the problem. If ye= s,<br> > >> capture the debug trace from a terminal to see where the prob= lem is.<br> > >> Look instructions here :<br> > >> <br> > >> <a href=3D"https://www.digikam.org/contribute/#freezes-and-ot= her-run-time-issues" rel=3D"noreferrer" target=3D"_blank">https://www.digik= am.org/contribute/#freezes-and-other-run-time-issues</a><br> > >> <br> > >> Best regards<br> > >> <br> > >> Gilles Caulier<br> > >> <br> > >> Le jeu. 16 juil. 2026 =C3=A0 03:31, Randolph M. Fritz <<a = href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>= > a<br> > >> <br> > >> =C3=A9crit :<br> > >> > I've got the "Write to item and XMP Sidecar&quo= t; setting turned on=E2=80=94is that<br> > >> <br> > >> OK?<br> > >> <br> > >> > Dates don't seem to be mentioned in the Advanced Met= adata panel; do I<br> > >> <br> > >> need to add them?<br> > >> <br> > >> > --<br> > >> > Randolph M. Fritz || <a href=3D"mailto:[email protected]= m" target=3D"_blank">[email protected]</a><br> > >> > <br> > >> > <br> > >> > On Wed, Jul 15, 2026 at 11:16=E2=80=AFAM Gilles Caulier = <<br> > >> <br> > >> <a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>> wrote:<br> > >> >> Yes the metadata sync to repopulate the date in the = database.<br> > >> >> <br> > >> >> But the most important point is to know where to tak= e the date in<br> > >> >> metadata in your case. There is a advanced metadata = panel in digiKam<br> > >> >> where you can customize that. Another point is to kn= ow if the XMP<br> > >> >> sidecar option need to be turned on.<br> > >> >> <br> > >> >> Best regards<br> > >> >> <br> > >> >> Gilles Caulier<br> > >> >> <br> > >> >> Le mer. 15 juil. 2026 =C3=A0 17:46, Randolph M. Frit= z <<a href=3D"mailto:[email protected]" target=3D"_blank">rmfritz3@gmai= l.com</a>><br> > >> <br> > >> a =C3=A9crit :<br> > >> >> > Thanks. I've been using mySQL internal whic= h, at least on the Mac,<br> > >> <br> > >> is in fact Maria.<br> > >> <br> > >> >> > Which option of the maintenance tool should I u= se? The metadata<br> > >> <br> > >> synchronizer? Or some other option?<br> > >> <br> > >> >> > --<br> > >> >> > Randolph M. Fritz || <a href=3D"mailto:rmfritz3= @gmail.com" target=3D"_blank">[email protected]</a><br> > >> >> > <br> > >> >> > On Wed, Jul 15, 2026, 4:51=E2=80=AFAM Gilles Ca= ulier <<br> > >> <br> > >> <a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>> wrote:<br> > >> >> >> Migrating the databases without dates will = not solve the problem.<br> > >> <br> > >> The<br> > >> <br> > >> >> >> items are not re-scanned.<br> > >> >> >> <br> > >> >> >> Try to run the maintenance tool and be forc= ed to scan all items.<br> > >> >> >> <br> > >> >> >> Note: MySQL has diverged from MariaDB in te= rms of compatibility,<br> > >> >> >> particularly with the latest versions of My= SQL. We strongly<br> > >> <br> > >> recommend<br> > >> <br> > >> >> >> using MariaDB instead of MySQL.<br> > >> >> >> <br> > >> >> >> Best regards<br> > >> >> >> <br> > >> >> >> Gilles Caulier<br> > >> >> >> <br> > >> >> >> Le mer. 15 juil. 2026 =C3=A0 07:20, Randolp= h M. Fritz <<br> > >> <br> > >> <a href=3D"mailto:[email protected]" target=3D"_blank">rmfri= [email protected]</a>> a =C3=A9crit :<br> > >> >> >> > Since no-one replied, I ran the migrat= ion and=E2=80=A6nothing happened.<br> > >> <br> > >> It didn't change the database in settings, and the dates = didn't reappear.<br> > >> Do I have to rebuild the database from scratch? How do I even= do that?<br> > >> <br> > >> >> >> > --<br> > >> >> >> > Randolph M. Fritz || <a href=3D"mailto= :[email protected]" target=3D"_blank">[email protected]</a><br> > >> >> >> > <br> > >> >> >> > <br> > >> >> >> > On Sun, Jul 12, 2026 at 8:38=E2=80=AFP= M Randolph M. Fritz <<br> > >> <br> > >> <a href=3D"mailto:[email protected]" target=3D"_blank">rmfri= [email protected]</a>> wrote:<br> > >> >> >> >> Or at least, the dates don=E2=80= =99t show up in the =E2=80=9CDates=E2=80=9D view.<br> > >> >> >> >> <br> > >> >> >> >> It=E2=80=99s an internal mySQL dat= abase. Is there any easy way to repair<br> > >> <br> > >> this? Or would it be better just to migrate to SQLite? (I hav= e 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 aga= inst 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> > >> >> >> >> Randolph M. Fritz || <a href=3D"ma= ilto:[email protected]" target=3D"_blank">[email protected]</a><br> <br> <br> <br> <br> </blockquote></div> --000000000000c9bb340656db1abb--