Created attachment 137134 [details]
Window in the background of the error message

We need the DebugView Log at startup as described here:

https://www.digikam.org/contribute/

Don't forget to set the debug variable.

Maik

(In reply to Maik Qualmann from comment #2)
> We need the DebugView Log at startup as described here:
> 
> https://www.digikam.org/contribute/
> 
> Don't forget to set the debug variable.
> 
> Maik

The relevant line from th estartup log is this one:
[10352] Error messages: "QMYSQL: Unable to execute query" "You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)" "1419" 2

(In reply to spam-receiver from comment #3)
> (In reply to Maik Qualmann from comment #2)
> > We need the DebugView Log at startup as described here:
> > 
> > https://www.digikam.org/contribute/
> > 
> > Don't forget to set the debug variable.
> > 
> > Maik
> 
> The relevant line from th estartup log is this one:
> [10352] Error messages: "QMYSQL: Unable to execute query" "You do not have
> the SUPER privilege and binary logging is enabled (you *might* want to use
> the less safe log_bin_trust_function_creators variable)" "1419" 2

The database user "digikam" has all privileges on the "digikam" database (except GRANT, of course), but globally only usage rights.

A little more log file would not be bad. The problem is on the MySQL server side and has to be fixed there. You don't have rights, probably to CREATE and DROP TABLE VIEW. You don't always have these rights automatically.

Maik

http://www.mysqlab.net/knowledge/kb/detail/topic/error+messages/id/5746

Maik

(In reply to Maik Qualmann from comment #5)
> A little more log file would not be bad. The problem is on the MySQL server
> side and has to be fixed there. You don't have rights, probably to CREATE
> and DROP TABLE VIEW. You don't always have these rights automatically.
> 
> Maik

I hope this helps:

[10352] digikam.general: Loading DrMinGw run-time...
[10352] digikam.general: DrMinGw run-time loaded.
[10352] digikam.general: DrMinGw crash-file will be located at:  "C:\\Users\\XXX\\AppData\\Local\\digikam_crash.log"
[10352] digikam.widgets: Breeze icons resource file found
[10352] digikam.widgets: Breeze-dark icons resource file found
[10352] QCommandLineParser: already having an option named "?"
[10352] QCommandLineParser: already having an option named "help-all"
[10352] QCommandLineParser: already having an option named "v"
[10352] digikam.general: Switch to widget style:  "Fusion"
[10352] digikam.general: AlbumWatch is disabled
[10352] digikam.general: Database Parameters:
[10352]    Type:                     "QMYSQL"
[10352]    DB Core Name:             "digikam"
[10352]    DB Thumbs Name:           "digikam"
[10352]    DB Face Name:             "digikam"
[10352]    DB Similarity Name:       "digikam"
[10352]    Connect Options:          ""
[10352]    Host Name:                "XXX"
[10352]    Host port:                3306
[10352]    Internal Server:          false
[10352]    Internal Server Path:     ""
[10352]    Internal Server Serv Cmd: ""
[10352]    Internal Server Init Cmd: ""
[10352]    Username:                 "digikam"
[10352]    Password:                 "XXXXXXX"
[10352] 
[10352] digikam.dbengine: Loading SQL code from config file "C:/Program Files/digiKam/data/digikam/database/dbconfig.xml"
[10352] digikam.dbengine: Checking XML version ID => expected:  3  found:  3
[10352] digikam.coredb: Core database: running schema update
[10352] digikam.coredb: Core database: have a structure version  10
[10352] digikam.coredb: Core database: makeUpdates  10  to  12
[10352] digikam.dbengine: Failure executing query:
[10352]  "" 
[10352] Error messages: "QMYSQL: Unable to execute query" "You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)" "1419" 2 
[10352] Bound values:  ()
[10352] digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV10ToV11" ] Statement [ "DROP TRIGGER IF EXISTS temp_insert_tagstree;" ]
[10352] digikam.coredb: Core database: schema update to V 11 failed!
[10352] digikam.coredb: Core database: cannot process schema initialization


Do you need even more?

On MySQL Server PC:

mysql -u USERNAME -p

set global log_bin_trust_function_creators=1;

Maik

(In reply to Maik Qualmann from comment #8)
> On MySQL Server PC:
> 
> mysql -u USERNAME -p
> 
> set global log_bin_trust_function_creators=1;
> 
> Maik

Hello Maik!
Thank you very much for your immediate response.

I checked this page if there are any security issues when the setting is changed:
https://mariadb.com/docs/reference/mdb/system-variables/log_bin_trust_function_creators/

It says:
Note that if ALL connections to this server ALWAYS use row-based binary logging, the security issues do not exist and the binary logging cannot break, so you can safely set this to TRUE

Hence, I checked the server settings and confirmed that binlog runs in ROW mode.

Now I changed the setting as you recommended and the schema upgrade passed, digikam started and requested the download of the face recognition data.
GREAT!

Not related to this issue, but maybe you can tell me:

Will the new face recognition function train itself from the faces which are already in the photos?

Is there a maintenance funtion to generate training data from the existing faces?

No, we do not automatically start the rebuilding of the training database. However, this must be carried out. In the maintenance tool in the section for face recognition, activate the option for rebuilding the training database and start the maintenance tool. All confirmed faces are used automatically, a special album selection is not necessary.

Do not forget to restart digiKam after successfully downloading the face model data.

Maik

Thank you very much again for your immediate help!

From my point of view this issue can be closed.

Thanks for the feedback.

Maik