[Digikam-devel] [digikam] [Bug 311041] MYSQL : scan faces fails because of missing table

via KDE Bugzilla bugzilla_noreply at kde.org
Thu Nov 19 15:01:20 GMT 2015


https://bugs.kde.org/show_bug.cgi?id=311041

caulier.gilles at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |http://commits.kde.org/digi
                   |                            |kam/74adf4f5dcdacc4b6574e61
                   |                            |f55dac956fa4c7611
   Version Fixed In|                            |5.0.0
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from caulier.gilles at gmail.com ---
Git commit 74adf4f5dcdacc4b6574e61f55dac956fa4c7611 by Gilles Caulier.
Committed on 19/11/2015 at 14:38.
Pushed by cgilles into branch 'master'.

First stage to fix Mysql support:

- For Internal server:
  Use the current system user to run mysql_installdb program to init local
database and server tables.
  The database is always installed in user account (~/.local/share/digikam/).
The goal is to set this install path configurable as with SQlite.
  Check the value returned to start init and sever program with QProcess. If
something is wrong abort the sequence and do not try to populate/use the
database.
  This will fix a crash if DB backend is null at digiKam shutdown.
  Fix the default embeded mysql server configuration to not need grant
privilege with index creation.

- For remote server:
  Fix the index creation procedure SQL statements to not check security rules.
No more grant privilege is required,
  excepted for the DB tables and the standard DB user dedicated for digiKam
use.
  Important : for a remote server, the database creation need to be instanced
by administrator, using following SQL statements (which will be put in DB setup
page later as helper):

  * For a common Mysql database storage :

  CREATE DATABASE digikamdb; GRANT ALL PRIVILEGES ON digikamdb.* TO
'digikam'@'localhost' IDENTIFIED BY 'digikam'; FLUSH PRIVILEGES;

  with:

  digikamdb       : the common database name (storing Core, Thumbnails, and
Face databases).
  digikam/digikam : the name/password of user account used by digiKam to access
on mysql server.

  * For separated Mysql database storages :

  CREATE DATABASE digikamcoredb; GRANT ALL PRIVILEGES ON digikamcoredb.* TO
'digikam'@'localhost' IDENTIFIED BY 'digikam'; FLUSH PRIVILEGES;
  CREATE DATABASE digikamthumbsdb; GRANT ALL PRIVILEGES ON digikamthumbsdb.* TO
'digikam'@'localhost' IDENTIFIED BY 'digikam'; FLUSH PRIVILEGES;
  CREATE DATABASE digikamfacedb; GRANT ALL PRIVILEGES ON digikamfacedb.* TO
'digikam'@'localhost' IDENTIFIED BY 'digikam'; FLUSH PRIVILEGES;

  with:

  digikamcoredb   : the Core database name.
  digikamthumbsdb : the Thumbnails database name.
  digikamfacedb   : the Face database name.
  digikam/digikam : the name/password of user account used by digiKam to access
on mysql server.

- The Face recognition database is now fully integrated in Mysql support. A new
settings have been add to DB setup page.
Related: bug 316747, bug 327062, bug 279580, bug 283502
FIXED-IN: 5.0.0

M  +29   -15   databaseserver/databaseserver.cpp
M  +4    -0    databaseserver/databaseserver.h

http://commits.kde.org/digikam/74adf4f5dcdacc4b6574e61f55dac956fa4c7611

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Digikam-devel mailing list