[digiKam-users] migrating to internal MySQL

[Maik Qualmann]

The internal server must already be started when you open the migration 
dialog. So you have to set up an internal server already in the digiKam 
settings. digiKam can only manage one internal server. Do not confuse internal 
server with a local MySQL server. The local MySQL server is set up as a remote 
one, just with localhost or 127.0.0.1 as the address. The internal server in 
digiKam launches another SQL server on your computer, which will also be 
stopped when you exit digiKam. However, if the internal server is located on 
an SSD, is connected over the socket file, is this the fastest database.

Maik

Am Donnerstag, 5. Juli 2018, 11:47:15 CEST schrieb karsten_df:
> Ok, so I tried the migration (using the 5.9.0 AppImage on Tumbleweed).
> I created a directory with full access to 'other' and pointed to this for
> the database directory.
> mysql_install_db and mysqld also seem to be pointed to correctly.
> On starting the migration, an error notification pops up: "Internal server
> is not used and is not active!"
> (There is also already a mysql server installed on my machine independently
> of digikam, however it makes no difference if this is running or stopped).
> 
> Does this work with the installed version of digikam only?
> (I'm not using this currently due to the issue described in
> http://digikam.1695700.n4.nabble.com/digiKam-users-Renaming-a-folder-does-no
> t-work-tp4705322.html)
> 
> Karsten
> 
> 
> Maik Qualmann wrote
> 
> > Yes, set up an internal server in digiKam. Everything is managed by
> > digiKam
> > (password, user name, etc.) A hidden MySQL directory is created in the
> > selected path. With the migration dialog you can transfer your existing
> > external database to the internal one.
> > 
> > Maik
> 
> --
> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html