https://bugs.kde.org/show_bug.cgi?id=388533
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|DUPLICATE |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=388533
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=388533
--- Comment #6 from Jyrki Soini ---
~> digikam-5.8.0-20180107T063018-x86-64.appimage
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
digikam.widgets: Breeze icons ressource file found
digikam.general: AlbumWatch u
https://bugs.kde.org/show_bug.cgi?id=388533
--- Comment #5 from Jyrki Soini ---
The errors I reported are against MariaDB 10.2.11.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388533
--- Comment #4 from Maik Qualmann ---
I have recreated this error (wrong foreign key constraint), but with MarioDB
there are no problems. We set FOREIGN_KEY_CHECKS=0, that should work. I will
see if I can find MySQL packages for my distribution.
Maik
https://bugs.kde.org/show_bug.cgi?id=388533
--- Comment #3 from Jyrki Soini ---
UpdateSchemaFromV7ToV9 still fails in
digikam-5.8.0-20180106T073314-x86-64.appimage
~> digikam-5.8.0-20180106T073314-x86-64.appimage
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available opt
https://bugs.kde.org/show_bug.cgi?id=388533
--- Comment #2 from Maik Qualmann ---
Ok, a little further. So we can not add CONSTRAINT if duplicate data already
exists. I see no other solution than to search for duplicate data and delete it
beforehand.
Maik
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=388533
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
Status|UNCONF
