[rt-users] DB entry encoding problem after upgrade

[Sven Sternberger]

Hallo!

ich empfehle die Lektuere der Datei UPGRADING.mysql (findet sich im RT
tar-ball)
Oder das lesen der Mailinglist Archive.

Sollte sich das jetzt etwas nach RTFM anhoeren, dann ..

Lieben Gruss!

sven


On Di, 2008-09-16 at 12:38 +0200, Christoph Szeppek wrote:
> Hi rt-users,
> 
> After upgrading from 3.6.6 to 3.8.1 every german umlaut in existing tickest
> is displayed incorrectly. Umlauts are displayed correctly if I create a new
> ticket so I asume there were some changes to the Decoder/Encoder (DB <->
> Decoder/Encoder <-> Email/Web) since 3.6.6.
> 
> To fix my DB encoding problem I would:
> - dump the affected rt tables (those needed for searching tickets, I don't
> care about the other tables)
> - decode them the old way
> - encode it the way it is now done
> - update the DB.
> 
> Could you please give me a hint on the DB encoding used in 3.6.1 so I can
> properly decode the old DB entries? Is it correct that the current DB
> encoding is utf-8?
> 
> Maybe the reason for my situation is that I did not install 3.8.1 from
> scratch, I upgraded from 3.6.6 to 3.8.1 by running "make upgrade" and
> extending the rt database by running "rt-test-dependencies" as suggestest by
> "make upgrade".
>