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

[Torben Nehmer]

Hi Jesse,

 

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.

 

I am not sure which MySQL Versions actually show this behavior. I suspect that it has to do with the actual Debian based installation I am using here. Maybe the MySQL System is forced to some charset or doesn't correctly honor the locale, maybe it is even a bug. I cannot tell for sure, unfortunalety.

 

Independent of this I think it is better to be safe than sorry, as the saying goes. 

 

 

Thanks again for the report.

 

No problem, please tell me if you need additional information and / or Tests regarding this problem. My RT 3.8 installation is still in testing, so doing all kinds of experimental Stuff is no problem. I'm waiting for 3.8.1 to go productive here ;-)

 

Greetings from Germany,
Torben Nehmer

-------
Torben Nehmer
Diplom Informatiker (FH)
Business System Developer

CANCOM Deutschland GmbH
Messerschmittstr. 20
89343 Scheppach
Germany

Tel.: +49 8225 - 996-1118
Fax: +49 8225 - 996-41118
torben.nehmer at cancom.de <mailto:torben.nehmer at cancom.de> 
www.cancom.de <http://www.cancom.de> 

CANCOM Deutschland GmbH
Sitz der Gesellschaft: Jettingen-Scheppach
HRB 10653 Memmingen
Geschäftsführer: Paul Holdschik, Christian Linder

Diese E-Mail und alle mitgesendeten Dateien sind vertraulich und ausschließlich für den Gebrauch durch den Empfänger bestimmt! 
This e-mail and any files transmitted with it are confidential intended solely for the use of the addressee!

 

Von: Jesse Vincent [mailto:jesse at bestpractical.com] 
Gesendet: Sonntag, 27. Juli 2008 02:15
An: Torben Nehmer
Cc: rt-users at lists.bestpractical.com
Betreff: Re: [rt-users] MySQL related Bugs in RT 3.8 while Upgrading from 3.6

 

 

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/20080728/2610e8fa/attachment.htm>