[Digikam-devel] [digikam] [Bug 279580] MYSQL : unable to get database to work after update to 2.0
via KDE Bugzilla
bugzilla_noreply at kde.org
Wed Nov 11 09:22:04 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=279580
--- Comment #7 from caulier.gilles at gmail.com ---
Patch against current implementation of XML config file :
--------------------------------------------------------------------------------------
diff --git a/data/database/dbconfig.xml.cmake.in
b/data/database/dbconfig.xml.cmake.in
index f4b3b05..e6adcb4 100644
--- a/data/database/dbconfig.xml.cmake.in
+++ b/data/database/dbconfig.xml.cmake.in
@@ -1054,6 +1054,7 @@
DROP PROCEDURE IF EXISTS create_index_if_not_exists;
</statement>
<statement mode="plain">
+ DELIMITER //
CREATE PROCEDURE create_index_if_not_exists(table_name_vc
varchar(50), index_name_vc varchar(50), field_list_vc varchar(1024))
SQL SECURITY INVOKER
BEGIN
@@ -1080,7 +1081,8 @@
EXECUTE stmt;
DEALLOCATE PREPARE stmt;
END IF;
- END;
+ END //
+ DELIMITER ;
</statement>
<statement mode="plain">CALL
create_index_if_not_exists('Images','dir_index','album');</statement>
<statement mode="plain">CALL
create_index_if_not_exists('Images','hash_index','uniqueHash');</statement>
@@ -1387,6 +1389,7 @@ ORDER BY inf.rating DESC, img.name ASC
DROP PROCEDURE IF EXISTS create_index_if_not_exists;
</statement>
<statement mode="plain">
+ DELIMITER //
CREATE PROCEDURE create_index_if_not_exists(table_name_vc
varchar(50), index_name_vc varchar(50), field_list_vc varchar(1024))
SQL SECURITY INVOKER
BEGIN
@@ -1413,7 +1416,8 @@ ORDER BY inf.rating DESC, img.name ASC
EXECUTE stmt;
DEALLOCATE PREPARE stmt;
END IF;
- END;
+ END //
+ DELIMITER ;
</statement>
<statement mode="plain">CALL
create_index_if_not_exists('UniqueHashes','id_uniqueHashes','thumbId');</statement>
<statement mode="plain">CALL
create_index_if_not_exists('FilePaths','id_filePaths','thumbId');</statement>
--------------------------------------------------------------------------------------
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list