https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #15 from Kusi ---
update procedure looks now more robust, thanks!
It doesn't address yet the issue about having a too long key as reported
initially and confirmed here:
https://mail.kde.org/pipermail/digikam-users/2016-August/022581.html
D
https://bugs.kde.org/show_bug.cgi?id=372312
Maik Qualmann changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=372312
Maik Qualmann changed:
What|Removed |Added
Attachment #102340|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #12 from Kusi ---
I've added my dbconfig.xml with which I was successful. In addition to the
modified dbconfig.xml, the following changes to the db were needed
- Since I have many Umlaute, accents etc in my db, I first had to fix the
encodi
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #11 from boospy ---
In the meantime it has worked for me too. What have i done. First i migrated do
sqlite. That seems to be not worked. No Pictures no data. Than i've created new
database and migrated the datas back and after this everythin
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #10 from Kusi ---
Created attachment 102342
--> https://bugs.kde.org/attachment.cgi?id=102342&action=edit
my dbconfig.xml
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372312
Maik Qualmann changed:
What|Removed |Added
Attachment #102330|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #8 from Kusi ---
the new dbconfig.xml brings me quite a bit further, but no success yet.
Unfortunately, I've got a 10 years old sql db which probably degenerated a bit.
I need to resolve all foreign key violations (from which I have a bunch)
https://bugs.kde.org/show_bug.cgi?id=372312
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #7 from Maik
https://bugs.kde.org/show_bug.cgi?id=372312
e.longuem...@laposte.net changed:
What|Removed |Added
CC||e.longuem...@laposte.net
--- Comment
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #5 from boospy ---
Migration to SQLite is also not possible. The idea was first migrate to sqlite
and then back to mysql.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372312
boospy changed:
What|Removed |Added
CC||li...@osit.cc
--- Comment #4 from boospy ---
Affected
https://bugs.kde.org/show_bug.cgi?id=372312
Kusi changed:
What|Removed |Added
CC||k...@forum.titlis.org
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #3 from Kusi ---
I deleted all but one row from the Albums table and tried to convert the
engine. Whats going on here?
MariaDB [digikamdb]> select * from Albums;
+--+---+--++-++--
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #2 from Kusi ---
The sql command in question
ALTER TABLE Albums
ADD CONSTRAINT Albums_AlbumRoots
FOREIGN KEY (albumRoot)
REFERENCES AlbumRoots (id) ON DELETE CASCADE ON UPDATE CASCADE, ADD UNIQUE
(albumRoot, relativePath(250)), E
https://bugs.kde.org/show_bug.cgi?id=372312
--- Comment #1 from Kusi ---
As mentioned on digikam-users mailing list on 2016-08-29, I tried the
alternative dbconfig.xml provided by Maik. No success. I've also tried
innodb-large-prefix=true in my global my.cfg. No success either. How can I help
to
16 matches
Mail list logo
