Version: 1.5.0 (using KDE 4.5.1) OS: Linux Since I installed Digikam new on my new system I can't create new tags anymore. They are not shown anyway and I get the following error in the console: "digikam(10172)/digikam (core) Digikam::TagEditDlg::createTAlbum: "some person" :: "some person" digikam(10172)/digikam (core) Digikam::DatabaseCoreBackendPrivate::debugOutputFailedQuery: Failure executing query: "UPDATE Tags SET rgt = rgt + 2 WHERE rgt > @myLeft;" Error messages: "Access denied; you need the SUPER privilege for this operation QMYSQL3: Unable to execute statement" 1227 2 "Access denied; you need the SUPER privilege for this operation" "QMYSQL3: Unable to execute statement" QSqlError(-1, "", "") Bound values: () QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-24358144' is still in use, all queries will cease to work." I'm using digikam 1.5 self compiled on kde with a mysql-server on the remote server. The user digikam has all rights granted for the database digikam. Reproducible: Always Steps to Reproduce: Create a tag Actual Results: Digikam shows the new tag in the list. The tag at the picture is any of my tags. Expected Results: There should be a new tag...
Something goes wrong with your dbms configuration. As the log output states you doesn't have enough privileges in the digikam schema: >"UPDATE Tags SET rgt = rgt + 2 WHERE rgt > @myLeft;" >Error messages: "Access denied; you need the SUPER privilege for this operation >QMYSQL3: Unable to execute statement" 1227 2 "Access denied; you need the SUPER Can you please check your dbms (mysql server) configuration? I had made some changes within the gsoc branch, which tries to detect permission problems by creating and manipulating a table. The question for me is, why it is needed to have SUPER privileges for this action. Besides of that, we have no other way to handle the tag hierachy - we need to use this kind of statements there.
With SUPER privileges it's working. But like you I'm wondering why this is needed :) Now I don't know wheather to close this bug or to leave it open since I guess you should not need SUPER privileges for the things digikam uses mysql.