#44991DB table COLLATION: disabled for ext_tables.sql but not for ext_tables_static+adt.sql
Description
Case I
When CHARSET is set (e.g. to utf8) for table in ext_tables.sql
CREATE TABLE tx_myext_domain_model_xyz ( uid int(11) unsigned NOT NULL auto_increment, [...] ) ENGINE=MyISAM CHARSET=utf8;
it is ignored while installing the extension in EM. A check with phpmyadmin shows that the collation is set to latin1_swedisch_ci instead.
I track this issue and found out in
namespace TYPO3\CMS\Install\Sql; SchemaMigrator::getUpdateSuggestions()
that COLLATION is not yet supported.
// Skip these special statements. TODO: collation support is currently disabled (needs more testing)
Case II
But when CHARSET is set for the same table in ext_tables_static+adt.sql (no need to insert static data),
DROP TABLE IF EXISTS tx_myext_domain_model_xyz; CREATE TABLE tx_myext_domain_model_xyz ( uid int(11) unsigned NOT NULL auto_increment, [...] ) ENGINE=MyISAM CHARSET=utf8;
then the COLLATION is set correctly to utf8_general_ci in DB.
For utf8 collation for use with TYPO3 CMS 6, are there drawbacks to only use ext_tables_static+adt.sql to hold tables ATM.