[TYPO3-dev] Weird Upgrade Problem 4.1.x -> 4.2.x

[Martin Kutschker]

Peter Russ schrieb:
> --- Original Nachricht ---
> Absender:   Steffen Müller
> Datum:       18.03.2009 11:23:
>> Hi.
>>
>> On 17.03.2009 11:38 Peter Russ wrote:
>>> On a system a new customer asked us to upgrade we experience weird
>>> upgrade problems with Mysql:
>>> MySQL 5.0.51 running on utf-8
>>>
>>
>> http://www.mysqlperformanceblog.com/2009/03/17/converting-character-sets/
>> I know this is slightly OT because it does not solve your problem. But
>> maybe this is of general interest for the charset/DB topic.
>>
>>
> 
> We solved the problem 'outside':
> 
> We opened the dump in kate, added required stuff to make db utf-8 and
> SAVED the complete dump in _utf-8_ format:
> 
> drop database if exists <dbname>;
> create database <debname> character set 'utf8' collate utf8_general_ci';
> set names 'utf8;
> use <dbname>;

This is the way. The problem was the difference between the connection
charset and the storage charset. The Core developers did not anticipate
such a setup (as it means the DB has to convert bewteen the charsets for
*every* SQL query).

I guess it should be mentioned somewhere that such a setup is not supported.

Masi