Posted by
bugzilla_noreply on
Nov 24, 2015; 3:02pm
URL: http://digikam.185.s1.nabble.com/Bug-283323-New-a-new-label-Digikam-root-tag-is-created-every-time-tp3871432p4682157.html
https://bugs.kde.org/show_bug.cgi?id=283323[hidden email] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CONFIRMED
--- Comment #66 from
[hidden email] ---
From Marcel Wiesweg, by private email :
"I believe the root of the problem is the TagsTree table. This table is only
maintained to allow searching in a tag including all child tags. In SQLite, it
always worked, in MySQL, there were problems and a solution with another tree
structure which I have never really understood.
This tree seems to create a lot of problems.
Alternative solution for the problem is to find in the C++ search code, all
child tags (readily available from TagsCache), and add them as bound values
(WHERE tagid IN (?,?,?....)).
This was limited for SQLite which only supports 999 bound values, and that
limit can be hit easily.
For MySQL, the limit appears to be 65536, which is feasible. Optimizations are
possible (using boost interval etc.)"
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel