#105540Mixed charsets in table defaults and text columns
Description
After upgrading from latin1 to utf8 via Update Wizard (it set’s utf8 and not utf8mb4!)
and applying
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['defaultTableOptions'] = [
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
];
Tables ended up in mixed scenarios where the columns used the desired charset options, but the table defaults were still defined to use the older charset and collation.
```
CREATE TABLE `sys_note` (
`uid` int(10) unsigned NOT NULL AUTO_INCREMENT,
`subject` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
`message` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
PRIMARY KEY (`uid`),
KEY `parent` (`pid`,`deleted`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
```Reviews 7
- main 91812[TASK] Disable db analyzer ac test in composer mode
- main 87757[BUGFIX] Respect column `CHARACTER SET` AND `COLLATE` in ext_tables.sql
- 13.4 88955[BUGFIX] Respect column `CHARACTER SET` AND `COLLATE` in ext_tables.sql
- 13.4 86961[TASK] Account for utf8 platform alias utf8mb3 in schema migrator tests
- main 86960[TASK] Account for utf8 platform alias utf8mb3 in schema migrator tests
- 13.4 86933[BUGFIX] Apply defaultTableOptions to CREATE TABLE DEFAULTS
- main 86880[BUGFIX] Apply defaultTableOptions to CREATE TABLE DEFAULTS