[Digikam-devel] [digikam] [Bug 355831] MySQL Schema Improvements

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355831

--- Comment #29 from caulier.gilles at gmail.com ---
>Did those errors cause the migration to fail? Or did it complete with just the complaints on the console?

==> No migration here. As now first run assistant support Mysql as well, we can
satrt to init a DB with Mysql as well. So, as schema is changed a lots, i
always start tests with a fresh DB.

>TokuDB should work and it would be possible to manually change all the tables after upgrade.
>If automatic support for a particular backend was required then I think it would have to be >specified on the setup/migration dialog and then manually specified during the migration.

==> in fact i don't care about TokuDB engine. If we specify in table creation
that Immno engine must be used as well, because we have tested with it only,
it's fine for me.

The question is more to kill this bug with right comment, as TokuDB engine is
not supported and digiKam use Inmmo engine. The goal is not to introduce
complexity, it's already enough complex.

As Mysql is able to support tables with different engines at the same time (fix
me if i'm wrong), digiKam must be usable as well. Right ?

Gilles

-- 
You are receiving this mail because:
You are the assignee for the bug.