Bug 351245

Summary: Unable to connect to mysql database, due to missing 'create trigger' while user has ALL privileges on digikam DBs
Product: [Applications] digikam Reporter: Gerard Dirkse <gerard.dirkse>
Component: Database-MysqlAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: grave CC: caulier.gilles, gerard.dirkse
Priority: NOR    
Version: 4.12.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 4.13.0
Attachments: Attachment 1, error message

Description Gerard Dirkse 2015-08-13 09:22:42 UTC 
When starting digikam, it complains that user has no CREATE TRIGGER privileges and doesnt connect to database (see attachment 1 [details]). Show grants for this user shows it has ALL priviledges on this database:

MariaDB [(none)]> show grants for 'digikam'@'%';
+-----------------------------------------------------------------------------------------------------------------------+
| Grants for digikam@%                                                                                                               |
+-----------------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'digikam'@'%' IDENTIFIED BY PASSWORD '*04E1D6'                    |
| GRANT ALL PRIVILEGES ON `digikam`.* TO 'digikam'@'%' WITH GRANT OPTION                |
| GRANT ALL PRIVILEGES ON `digikam_thumbs`.* TO 'digikam'@'%' WITH GRANT OPTION  |
+-----------------------------------------------------------------------------------------------------------------------+
3 rows in set (0.01 sec)


Reproducible: Always

Steps to Reproduce:
1. Start digikam
2.
3.

Actual Results:  
Refer to attachment 1 [details], no contents

Expected Results:  
Show current libraries of fotos
Comment 1 Gerard Dirkse 2015-08-13 09:24:18 UTC 
Created attachment 94013 [details]
Attachment 1 [details], error message

Error message when starting up digikam.
Comment 2 Gerard Dirkse 2015-08-17 06:43:59 UTC 
Problem fixed, due to binary-logging of database, SUPER privilege was required.  After adding SUPER privilege to user problem was gone.