[rt-users] MySQL related Bugs in RT 3.8 while Upgrading from 3.6

[Jesse Vincent]

On Jul 24, 2008, at 2:58 AM, Torben Nehmer wrote:

> Hi there,
>
> I have been testing the upgrade of our (originally Debian Based) RT  
> 3.6.5 installation to RT 3.8 and found two bugs in the process:
>
> First, the script generating the necessary code to convert the  
> Database from MySQL 4.0 to 4.1 and newer produces corrupt SQL at  
> least in my case here. It has several occurrences of constructs like  
> this:
>

Thank you. I've opened a ticket for this.

>
> The second problem I have tested so far only with the RT Standalone  
> server, I cannot say anything (yet) for other ways to run RT as I’m  
> still in the process of testing everything.
>
> At least Debian MySQL 5.0.51a does by default initialize all  
> connections in latin1 mode. So after converting the Database to  
> correct UTF-8, MySQL does automatically convert any columns known as  
> UTF-8 into the default connection charset latin1. This leads to all  
> broken non-ASCII Chars all over the site except the Attachments  
> (where RT itself appearantly does the conversion handling, as this  
> is a BINARY field).

How long has MySQL done that? I've never experienced it. Regardless,  
I've opened a ticket for this as well.

Thanks again for the report.

Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20080726/260e37fc/attachment.htm>