Feature #55429
closed
Install tool should check database "collation"
0%
Description
Recently we ran into some problems with solr and it showed up the whole cause of a series of strange issues was that the database collation (and thus any collation of newly created tables) was set to "latin1_swedish_ci".
Maybe there should be a check in the install tool (or even in the start-screen after login) which warns a user/admin of a wrong collation being set.
I guess nowaday the collation utf8_general_ci should be set by default.
This issue is especially a problem for fields holding serialized objects/data array. Unserializing them doesn't work because data seems to get garbled when being converted from latin1 to utf8.
Maybe this check should also be made for every table on its own to detect "Altlasten" when upgrading an existing installation.
Updated by Bernhard Kraft almost 11 years ago
Another solution (at least for serialized fields) would be to set them to "binary" collation. If doing this from phpmyadmin the field will become a blob.
So I think fields whose intent is to get used as storage for serialized data should rather be "blob" or "longblob" instead of "text".
Updated by Alexander Opitz about 9 years ago
- Target version changed from 6.2.0 to 8 LTS
Updated by Morton Jonuschat about 8 years ago
- Status changed from New to Resolved
- Target version changed from 8 LTS to 8.4
This has been solved in TYPO3 8/master with the switch to Doctrine. If no explicit charset and/or collation have been specified the default will be 'utf8' and 'utf8_unicode_ci'.
There's also a check in the install tool that checks for some common UTF8 setup problems.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed