[digikam] [Bug 372312] database upgrade v7 to v8 failed

[Kusi]

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

--- Comment #2 from Kusi <kusi at forum.titlis.org> ---
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)), ENGINE InnoDB;

runs fine without specifying the engine, that is without "ENGINE InnoDB". On my
db, according to

  SHOW TABLE STATUS FROM digikamdb;

the "Albums" table is of engine type MyISAM, not InnoDB. Is that new db engine
format wanted? Is it ok to change the engine of an existing table? It looks
like I have inconsistent engine types over all my tables (mixture between
MyISAM and InnoDB).

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