[TYPO3-core] RFC: Bug #5088: cache is not saved properly because of charset conflict in the database

[Martin Kutschker]

Michael Stucki schrieb:
> This is a SVN patch request.
> 
> Problem:
> There is a serious bug that blocks TYPO3 4.1 completely. See below on how to
> reproduce this...
> 
> Solution:
> The bug is caused by a change in the schema of the cache_hash table. The
> field "content" was changed from "mediumblob" into "mediumtext", which
> meanns that the content will be converted into the chosen character set.
> However, this will fail if the page template contains characters from a
> different character set.
> 
> The solution is to simply change the field type of cache_hash.content from
> "mediumtext" back to "mediumblob".
> 
> How to reproduce:
> 
> | Here is a list of prerequisites:
> | - The backend must run in latin1 (no forceCharset=utf8 set!)
> | - setDBinit=SET NAMES utf8;
> | - cache_hash.content = utf8_general_ci
> | - Your template contains two page types (typeNum)
> | - Your template contains special characters
> | 
> | Changing a single one of these requirements makes the bug go away.

But with SET NAMES utf8 you set the mysql client encoding to UTF8. Mysql 
client encoding and BE encoding must match.

Masi