[Digikam-devel] [Bug 160966] some searches don't work properly with the new sqlite3-3.5.8

Arnd Baecker arnd.baecker at web.de
Wed Jun 18 22:08:39 BST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=160966         




------- Additional Comments From arnd.baecker web de  2008-06-18 23:08 -------
I don't see how this is a way to hell, there are surely much worse sins ...

There were already several users reporting problems which were caused by this particular sqlite issue, however finding the real cause in each of these
causes did take some time; also many users might not report such an
issue and just discard digikam ("it is just too slow ...").
This is why this sqlite was included.
Still, IMO the proper solution is the version check. 
Jan, do you have an idea how to do that?

Actually, another (less optimal) option might
be a runtime check of the used sqlite and prevent digikam from starting
with 3.5.8. What do you think Gilles?



More information about the Digikam-devel mailing list