Bug #82075 sakila sample DB has a MyISAM table
Submitted: 1 Jul 2016 1:03 Modified: 20 Jul 2016 23:57
Reporter: Alfredo Kojima Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[1 Jul 2016 1:03] Alfredo Kojima 
Description:
The sakila sample DB has a MyISAM table, probably because InnoDB didn't support FULLTEXT indexes back then.

Now that FULLTEXT works since 5.6 and since Group Replication doesn't support MyISAM, it would be good to update the model to use InnoDB everywhere.

How to repeat:
grep MyISAM sakila-schema.sql

Suggested fix:
s/MyISAM/InnoDB/
[1 Jul 2016 3:46] MySQL Verification Team 
Hello Alfredo Kojima,

Thank you for the report and feedback!

Thanks,
Umesh
[20 Jul 2016 23:57] Philip Olson 
This is now fixed, and here is the Sakila v1.1 changelog entry:

    Removed all MyISAM references. The film_text table, and it's
    FULLTEXT definition, now only uses InnoDB. If you use an older
    MySQL server version (5.6.10 and lower) then we recommend
    upgrading MySQL. If you can not upgrade, then change the
    film_text ENGINE to MyISAM in the
    sakila-schema.sql SQL file.

Thank you for the bug report.