Re: Dates missing from my digiKam database

This is currently a MariaDB issue; it affects openSUSE Tumbleweed as well.=
=20
That=E2=80=99s simply the downside of using cutting-edge software sometimes.

Maik

Am Freitag, 24. Juli 2026, 15:53:43 Mitteleurop=C3=A4ische Sommerzeit schri=
eb=20
Gilles Caulier:
> Create a new account on your system and run from scratch digiKAm on a
> small collection.
>=20
> Gilles Caulier
>=20
> Le ven. 24 juil. 2026 =C3=A0 15:50, Randolph M. Fritz <[email protected]=
> a=20
=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 thr=
ow
> > away my existing database of, literally, decades of images.
> >=20
> > How do I run this test without losing all my data?
> > --
> > Randolph M. Fritz || [email protected]
> >=20
> > On Thu, Jul 23, 2026 at 12:03=E2=80=AFPM Randolph M. Fritz <rmfritz3@gm=
ail.com>=20
wrote:
> >> Tried this with 9.2.0; same error, fell back to 9.1.0 again.
> >>=20
> >> I'm just relieved I didn't have to roll my database all the way back.
> >> --
> >> Randolph M. Fritz || [email protected]
> >>=20
> >> On Mon, Jul 20, 2026 at 9:56=E2=80=AFPM Randolph M. Fritz <rmfritz3@gm=
ail.com>=20
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 the
> >>> following error: (I have a screenshot, too, but it's too big for the
> >>> mailing list)>>>=20
> >>>> An error occurred during the internal server start.
> >>>> Details:
> >>>> Could not start database initializer.
> >>>> Executable: /Applications/digiKam.org/digikam.app/Contents/lib/maria=
db/
> >>>> 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_data
> >>>> Process error: Unknown error
> >>>> Please check the database settings in this dialog.
> >>>=20
> >>> A bit of poking at the command line suggests a missing symlink in the
> >>> application bundle, but I really don't know for certain. --
> >>> Randolph M. Fritz || [email protected]
> >>>=20
> >>> On Fri, Jul 17, 2026 at 11:27=E2=80=AFPM Gilles Caulier=20
<[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 ?
> >>>>=20
> >>>> Best regards
> >>>>=20
> >>>> Gilles Caulier
> >>>>=20
> >>>> Le sam. 18 juil. 2026 =C3=A0 06:29, Randolph M. Fritz <rmfritz3@gmai=
l.com> a=20
=C3=A9crit :
> >>>> > Unfortunately, no, that version does not fix the problem.
> >>>> > --
> >>>> > Randolph M. Fritz || [email protected]
> >>>> >=20
> >>>> > On Thu, Jul 16, 2026 at 9:37=E2=80=AFPM Maik Qualmann <metzpinguin=
@gmail.com>=20
wrote:
> >>>> >> The issue with the date view should be fixed in the digiKam-9.2.0
> >>>> >> pre-release; please test it here:
> >>>> >>=20
> >>>> >> https://files.kde.org/digikam/
> >>>> >>=20
> >>>> >> Maik
> >>>> >>=20
> >>>> >> Am Freitag, 17. Juli 2026, 06:03:22 Mitteleurop=C3=A4ische Sommer=
zeit
> >>>> >> schrieb
> >>>> >>=20
> >>>> >> 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.
> >>>> >> >=20
> >>>> >> > > 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.
> >>>> >> > >=20
> >>>> >> > > 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]
> >>>> >> > >=20
> >>>> >> > >=20
> >>>> >> > > On Thu, Jul 16, 2026 at 1:52=E2=80=AFAM Gilles Caulier
> >>>> >> > > <[email protected]>
> >>>> >> > >=20
> >>>> >> > > wrote:
> >>>> >> > >> In fact this depend of multiple parameters.
> >>>> >> > >>=20
> >>>> >> > >> 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 t=
he
> >>>> >> > >> date
> >>>> >> > >> must be populated in all cases in the database.
> >>>> >> > >>=20
> >>>> >> > >> I recommend creating a small collection for testing and to
> >>>> >> > >> populate a
> >>>> >> > >> small database with it. You must reproduce the problem. If y=
es,
> >>>> >> > >> capture the debug trace from a terminal to see where the
> >>>> >> > >> problem is.
> >>>> >> > >> Look instructions here :
> >>>> >> > >>=20
> >>>> >> > >> https://www.digikam.org/contribute/#freezes-and-other-run-ti=
me-> >>>> >> > >> issues
> >>>> >> > >>=20
> >>>> >> > >> Best regards
> >>>> >> > >>=20
> >>>> >> > >> Gilles Caulier
> >>>> >> > >>=20
> >>>> >> > >> Le jeu. 16 juil. 2026 =C3=A0 03:31, Randolph M. Fritz
> >>>> >> > >> <[email protected]> a
> >>>> >> > >>=20
> >>>> >> > >> =C3=A9crit :
> >>>> >> > >> > I've got the "Write to item and XMP Sidecar" setting turned
> >>>> >> > >> > on=E2=80=94is that
> >>>> >> > >>=20
> >>>> >> > >> OK?
> >>>> >> > >>=20
> >>>> >> > >> > Dates don't seem to be mentioned in the Advanced Metadata
> >>>> >> > >> > panel; do I
> >>>> >> > >>=20
> >>>> >> > >> need to add them?
> >>>> >> > >>=20
> >>>> >> > >> > --
> >>>> >> > >> > Randolph M. Fritz || [email protected]
> >>>> >> > >> >=20
> >>>> >> > >> >=20
> >>>> >> > >> > On Wed, Jul 15, 2026 at 11:16=E2=80=AFAM Gilles Caulier <
> >>>> >> > >>=20
> >>>> >> > >> [email protected]> wrote:
> >>>> >> > >> >> Yes the metadata sync to repopulate the date in the
> >>>> >> > >> >> database.
> >>>> >> > >> >>=20
> >>>> >> > >> >> 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.
> >>>> >> > >> >>=20
> >>>> >> > >> >> Best regards
> >>>> >> > >> >>=20
> >>>> >> > >> >> Gilles Caulier
> >>>> >> > >> >>=20
> >>>> >> > >> >> Le mer. 15 juil. 2026 =C3=A0 17:46, Randolph M. Fritz
> >>>> >> > >> >> <[email protected]>
> >>>> >> > >>=20
> >>>> >> > >> a =C3=A9crit :
> >>>> >> > >> >> > Thanks. I've been using mySQL internal which, at least =
on
> >>>> >> > >> >> > the Mac,
> >>>> >> > >>=20
> >>>> >> > >> is in fact Maria.
> >>>> >> > >>=20
> >>>> >> > >> >> > Which option of the maintenance tool should I use? The
> >>>> >> > >> >> > metadata
> >>>> >> > >>=20
> >>>> >> > >> synchronizer? Or some other option?
> >>>> >> > >>=20
> >>>> >> > >> >> > --
> >>>> >> > >> >> > Randolph M. Fritz || [email protected]
> >>>> >> > >> >> >=20
> >>>> >> > >> >> > On Wed, Jul 15, 2026, 4:51=E2=80=AFAM Gilles Caulier <
> >>>> >> > >>=20
> >>>> >> > >> [email protected]> wrote:
> >>>> >> > >> >> >> Migrating the databases without dates will not solve t=
he
> >>>> >> > >> >> >> problem.
> >>>> >> > >>=20
> >>>> >> > >> The
> >>>> >> > >>=20
> >>>> >> > >> >> >> items are not re-scanned.
> >>>> >> > >> >> >>=20
> >>>> >> > >> >> >> Try to run the maintenance tool and be forced to scan =
all
> >>>> >> > >> >> >> items.
> >>>> >> > >> >> >>=20
> >>>> >> > >> >> >> Note: MySQL has diverged from MariaDB in terms of
> >>>> >> > >> >> >> compatibility,
> >>>> >> > >> >> >> particularly with the latest versions of MySQL. We
> >>>> >> > >> >> >> strongly
> >>>> >> > >>=20
> >>>> >> > >> recommend
> >>>> >> > >>=20
> >>>> >> > >> >> >> using MariaDB instead of MySQL.
> >>>> >> > >> >> >>=20
> >>>> >> > >> >> >> Best regards
> >>>> >> > >> >> >>=20
> >>>> >> > >> >> >> Gilles Caulier
> >>>> >> > >> >> >>=20
> >>>> >> > >> >> >> Le mer. 15 juil. 2026 =C3=A0 07:20, Randolph M. Fritz <
> >>>> >> > >>=20
> >>>> >> > >> [email protected]> a =C3=A9crit :
> >>>> >> > >> >> >> > Since no-one replied, I ran the migration and=E2=80=
=A6nothing
> >>>> >> > >> >> >> > happened.
> >>>> >> > >>=20
> >>>> >> > >> It didn't change the database in settings, and the dates did=
n't
> >>>> >> > >> reappear.
> >>>> >> > >> Do I have to rebuild the database from scratch? How do I even
> >>>> >> > >> do that?
> >>>> >> > >>=20
> >>>> >> > >> >> >> > --
> >>>> >> > >> >> >> > Randolph M. Fritz || [email protected]
> >>>> >> > >> >> >> >=20
> >>>> >> > >> >> >> >=20
> >>>> >> > >> >> >> > On Sun, Jul 12, 2026 at 8:38=E2=80=AFPM Randolph M. =
=46ritz <
> >>>> >> > >>=20
> >>>> >> > >> [email protected]> wrote:
> >>>> >> > >> >> >> >> Or at least, the dates don=E2=80=99t show up in the=
 =E2=80=9CDates=E2=80=9D
> >>>> >> > >> >> >> >> view.
> >>>> >> > >> >> >> >>=20
> >>>> >> > >> >> >> >> It=E2=80=99s an internal mySQL database. Is there a=
ny easy way
> >>>> >> > >> >> >> >> to repair
> >>>> >> > >>=20
> >>>> >> > >> this? Or would it be better just to migrate to SQLite? (I ha=
ve
> >>>> >> > >> 653 GB of
> >>>> >> > >> image files.)
> >>>> >> > >>=20
> >>>> >> > >> >> >> >>> 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
> >>>> >> > >> >> >> >>=20
> >>>> >> > >> >> >> >> --
> >>>> >> > >> >> >> >> Randolph M. Fritz || [email protected]