Bug 331628 - MYSQL : digiKam talk's uncompatible SQL with TokuDB database engine
Summary: MYSQL : digiKam talk's uncompatible SQL with TokuDB database engine
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (show other bugs)
Version: 3.5.0
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-28 20:00 UTC by the
Modified: 2015-12-02 21:30 UTC (History)
1 user (show)

See Also:
Latest Commit: http://commits.kde.org/digikam/3eefa0b7493ee7abb72d6532e618a3769e181e2f
Version Fixed In: 5.0.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description the 2014-02-28 20:00:06 UTC 
after 7% creation of schemas stop's,.. about 10 tables initilized to tokudb tables,
no thumb nale records.

Same system/config whit Aria,... engines works. Problem could related blob's, large data ?
Comment 1 caulier.gilles 2015-06-25 13:06:46 UTC 
New digiKam 4.11.0 is available with official PKG installer for OSX.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 2 caulier.gilles 2015-12-02 21:30:27 UTC 
Git commit 3eefa0b7493ee7abb72d6532e618a3769e181e2f by Gilles Caulier.
Committed on 02/12/2015 at 21:28.
Pushed by cgilles into branch 'master'.

Apply patch #95866 to force use of InnoDB engine with all Mysql database table.
Related: bug 281838, bug 355831
FIXED-IN: 5.0.0

M  +3    -1    NEWS
M  +40   -21   data/database/dbconfig.xml.cmake.in

http://commits.kde.org/digikam/3eefa0b7493ee7abb72d6532e618a3769e181e2f