Re: Dates missing from my digiKam database

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]> =
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 a=
way 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@gmai=
l.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@gmai=
l.com> wrote:
>>>
>>> No, I just tried 9.2.0. I fell back to 9.1.0. I have now attempted to c=
reate a new database on a small collection, and the attempt drew the follow=
ing error: (I have a screenshot, too, but it's too big for the 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/ Co=
ntents/Resources/digikam/database/mysql-global.conf, --basedir=3D/ Applicat=
ions/digiKam.org/digikam.app/Contents/lib/mariadb/, --datadir=3D/
>>>> Users/randolph/Documents/dktest/.mysql.digikam/db_data
>>>> 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 the a=
pplication 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 <caulier.gilles=
@gmail.com> 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 <rmfritz3@gmail.=
com> 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 <metzpinguin@g=
mail.com> wrote:
>>>> >>
>>>> >> The issue with the date view should be fixed in the digiKam-9.2.0 p=
re-release;
>>>> >> please test it here:
>>>> >>
>>>> >> https://files.kde.org/digikam/
>>>> >>
>>>> >> Maik
>>>> >>
>>>> >> Am Freitag, 17. Juli 2026, 06:03:22 Mitteleurop=C3=A4ische Sommerze=
it schrieb
>>>> >> Randolph M. Fritz:
>>>> >> > I should add at this point that I can see dates in the file prope=
rties, 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 dat=
es in the
>>>> >> > > display.
>>>> >> > >
>>>> >> > > How do I query the internal mysql database? I'm suspecting at t=
his point
>>>> >> > > that the dates are actually in the database, but not being disp=
layed; 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 <caulier=
[email protected]>
>>>> >> > >
>>>> >> > > wrote:
>>>> >> > >> In fact this depend of multiple parameters.
>>>> >> > >>
>>>> >> > >> What I don't understand is why the data is not populated in th=
e
>>>> >> > >> database. If date of shoot cannot be taken from the file metad=
ata
>>>> >> > >> 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 pop=
ulate a
>>>> >> > >> small database with it. You must reproduce the problem. If yes=
,
>>>> >> > >> capture the debug trace from a terminal to see where the probl=
em 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 <rmfritz=
[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 pa=
nel; 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 databas=
e.
>>>> >> > >> >>
>>>> >> > >> >> But the most important point is to know where to take the d=
ate in
>>>> >> > >> >> metadata in your case. There is a advanced metadata panel i=
n digiKam
>>>> >> > >> >> where you can customize that. Another point is to know if t=
he XMP
>>>> >> > >> >> sidecar option need to be turned on.
>>>> >> > >> >>
>>>> >> > >> >> Best regards
>>>> >> > >> >>
>>>> >> > >> >> Gilles Caulier
>>>> >> > >> >>
>>>> >> > >> >> Le mer. 15 juil. 2026 =C3=A0 17:46, Randolph M. Fritz <rmfr=
[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 me=
tadata
>>>> >> > >>
>>>> >> > >> 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 al=
l items.
>>>> >> > >> >> >>
>>>> >> > >> >> >> Note: MySQL has diverged from MariaDB in terms of compat=
ibility,
>>>> >> > >> >> >> particularly with the latest versions of MySQL. We stron=
gly
>>>> >> > >>
>>>> >> > >> 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=A6=
nothing 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. Fr=
itz <
>>>> >> > >>
>>>> >> > >> [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 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]
>>>> >>
>>>> >>
>>>> >>
>>>> >>