[Rt-devel] Migrating RT DB from mysql 4.1.11 to 5.0.51

[Ruslan Zakirov]

Don't dump it using latin1, but use binary:
--default-character-set=binary . If dump still fails then it's totally
mysql problem.

On Wed, May 20, 2009 at 7:16 PM,  <Arnas.Kupsys at swisscom.com> wrote:
> We already look into the perl script to migrate to utf8.
>
> Arnas
>
> -----Original Message-----
> From: rt-devel-bounces at lists.bestpractical.com [mailto:rt-devel-bounces at lists.bestpractical.com] On Behalf Of Vick Khera
> Sent: Wednesday, May 20, 2009 4:24 PM
> To: rt-devel at lists.bestpractical.com
> Subject: Re: [Rt-devel] Migrating RT DB from mysql 4.1.11 to 5.0.51
>
>> On Tue, May 19, 2009 at 5:40 PM,  <Arnas.Kupsys at swisscom.com> wrote:
>>> Hello we are running RT for our company's day to day request handling, and customer center issue logging.
>>> We want to migrate RT DB to a new machine (newer OS and new mysql version).
>>> But facing the problems due to the big DB size and table encodings.
>
> We recently upgraded from Postgres 8.0 (or 8.1 I don't recall which) to 8.3, which had stricted UTF-8 checking, and we had to manually go in and fix up all the UTF-8 errors that were allowed to creep in.  It was painful, but scripting it helped a lot... :-)
>
> It sounds really like you have a mysql bug.  It seems the correct forum for you is where you filed your bug report.
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
>



-- 
Best regards, Ruslan.