[digiKam-users] MySQL internal

Maik Qualmann metzpinguin at gmail.com
Mon Sep 3 06:52:57 BST 2018

There is nothing missing in the screencast. You see the complete change from 
SQlite to internal MySQL. The database is automatically created by digiKam if 
it does not already exist. This happens at the point where you select internal 
MySQL and exit the setup with OK. Again, to understand, internal MySQL has 
nothing to do with a running local MySQL server. DigiKam creates the database 
and a server instance itself and terminates it. The communication is via a 
socket file.


Am Sonntag, 2. September 2018, 02:07:26 CEST schrieb digikam at 911networks.com:
> On Sat, 01 Sep 2018 23:07:55 +0200
> Maik Qualmann <metzpinguin at gmail.com> wrote:
> > Here is the link to the screencast. It takes a while for Google to
> > encode the video in all sizes and it's sharp. The demo only uses a
> > very small SQlite collection.
> > 
> > https://drive.google.com/file/d/1t6u1emc8_x8thZGsYZ64Ve3-kZ1ApFO7/view?
> > usp=sharing
> > 
> > Maik
> Thank you. I will be trying the conversion over the weekend.
> I was missing the 1st step which is to create the database in the
> config tools.
> Thank you very much. Maybe the video should be posted somewhere on
> digikam.kde

More information about the Digikam-users mailing list