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

[Martin Kutschker]

Steffen Müller schrieb:
> Hi Masi,
> 
> On 18.03.2009 13:31 Martin Kutschker wrote:
>> 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).
>>
> 
> Is there a way to find out if there is any conversion?

Have a look at your own posting:

mysql> SHOW VARIABLES LIKE 'character_set%';
+--------------------------+----------------------------+
| Variable_name            | Value                      |
+--------------------------+----------------------------+
| character_set_client     | latin1                     |
| character_set_connection | latin1                     |
| character_set_database   | utf8                       |
| character_set_results    | latin1                     |
| character_set_server     | latin1                     |
+--------------------------+----------------------------+

These variables should show the same charset. And this charset must be
the same as the one TYPO3 uses (note that Mysql uses the synonyms latin1
and utf8 while TYPO3 has iso-8859-1 and utf-8).

Masi