https://bugs.kde.org/show_bug.cgi?id=447416
Bug ID: 447416
Summary: Unable to use mariadb 10 remote database with digikam
7.3
Product: digikam
Version: 7.3.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: mattia.ve...@tiscali.it
Target Milestone: ---
I had a working digikam 7.2 installation (from Fedora Linux 35 RPMs) with a
remote MariaDB 5.x database on a Qnap NAS. Things still worked after I migrated
the database to MariaDB 10.x on the same NAS.
After the upgrade to digikam 7.3 (always Fedora Linux RPMs) at startup I got:
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 12
digikam.coredb: Core database: makeUpdates 12 to 13
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Column count of mysql.proc
is wrong. Expected 21, found 20. Created with MariaDB 50544, now running
100508. Please use mariadb-upgrade to fix this error" "1558" 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ]
Statement [ "\n DROP PROCEDURE IF EXISTS
create_index_if_not_exists;\n " ]
digikam.coredb: Core database: schema update to V 13 failed!
digikam.coredb: Core database: cannot process schema initialization
I made several attempts to export/import the database and to drop the db and
let digikam 7.3 recreate it, but it always fails.
So, I started from scratch: downgraded Digikam to 7.2, start Digikam from clean
and let it create a local SQLite database. After that I've upgraded Digikam to
7.3, started with the local SQLite database and tried to run the migration tool
to the newly created MariaDB on NAS, but I get:
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: no database file available
digikam.dbengine: Failure executing query:
""
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
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "CreateTriggers" ] Statement
[ "CREATE TRIGGER insert_tagstree AFTER INSERT ON Tags FOR EACH ROW\n
INSERT INTO TagsTree SELECT NEW.id, NEW.pid\n
UNION SELECT NEW.id, pid FROM TagsTree WHERE id = NEW.pid;\n " ]
Downgrading Digikam to 7.2 and running the migration tool succeeds, but then I
return to the initial "schema update failed" error...
Version of components:
digikam-7.2.0-5.fc35
digikam-7.3.0-4.fc35
MariaDB 10.5.8
--
You are receiving this mail because:
You are watching all bug changes.
