Re: Dates missing from my digiKam database

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-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 Metadata panel; do I nee=
d to add them?
> --
> Randolph M. Fritz || [email protected]
>
>
> On Wed, Jul 15, 2026 at 11:16=E2=80=AFAM Gilles Caulier <caulier.gilles@g=
mail.com> 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]=
m> 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 synchr=
onizer? Or some other option?
>> >
>> > --
>> > Randolph M. Fritz || [email protected]
>> >
>> > On Wed, Jul 15, 2026, 4:51=E2=80=AFAM Gilles Caulier <caulier.gilles@g=
mail.com> 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 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. Fritz <rmfritz3@gmail=
.com> a =C3=A9crit :
>> >> >
>> >> > Since no-one replied, I ran the migration and=E2=80=A6nothing happe=
ned. It didn't change the database in settings, and the dates didn't reappe=
ar. 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 <rmfritz3=
@gmail.com> 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]
>> >
>> >
>> >
>> >
>> >