Hi,

I reported the same problem here (but nobody answered):
http://lists.bestpractical.com/pipermail/rt-users/2008-August/053512.html

I think there is a lack in the mysql upgrade document or in the upgrade
script.
I did it on a test environment and didn't have time to find out the real
solution,
so I delayed the migration of the real system.

Some more information:
- After migration, new entries (for example CF-s) seemed good, even if they
have non-ascii characters.
- In mysql CLI:   show variables like 'c%'   shows that everything is utf8
(so this seems good)

Any suggestion?

Thanks,
--
Bekény


On Tue, Sep 2, 2008 at 5:28 PM, Emmanuel Lacour <[EMAIL PROTECTED]>wrote:

> On Tue, Sep 02, 2008 at 08:14:55AM -0700, F350 wrote:
> >
> > Thanks a lot for your help and time Emmanuel.
> > I updated all the tickets, CF and templates that look corrupted.
> > Next time i'll make sure I do the updates on a test server :)
> >
>
> You're welcome :)
>
> Using a test server or a test db/rt instance is a must have ;)
> _______________________________________________
>
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Reply via email to