Welcome to the FogBugz Knowledge Exchange

Question

1

FB6 had an issue storing non-latin characters in cases when using MySQL as the backend due to the MySQL ODBC connector. Since FB7 is .NET and can use the MySQL.NET provider, does FB7 correctly handle non-latin character set input when using MySQL?

Related MySQL bug.

flag	asked Nov 2 2009 at 22:45 jasonjwwilliams 355●1●9

We didn't really have problems with it. We just stored the non-latins in the database encoded. Really only became an issue when you moved from Linux to Windows. – Rich Armstrong♦ Nov 6 2009 at 23:05

Ted · Answer 1 · 2009-11-03 16:50:07Z UTC

1

Everything should work in 7. I've tested it with a wide variety of characters outside the normal Latin range.

answered Nov 3 2009 at 16:50

Ted♦♦
4,880●3●10

jasonjwwilliams · Accepted Answer · 2010-05-24 17:33:35Z UTC

1

On our FB7 install the answer is definitely no...FogBugz does not handle non-latin correctly on MySQL. The resolution was to move to FogBugz On Demand. The issue is that FB7 has a hack in place from when MySQL did not support UTF-8 (MySQL < 5.0). They encode non-latin to operate inside a MySQL latin-1 encoding...which makes it difficult to determine why this is not operating correctly.

answered May 24 2010 at 17:33

jasonjwwilliams
355●1●9

It sounds like you've moved to FogBugz On Demand, but another thing that may be worth inspecting is the not only the charset of the tables in MySQL, but also the charset used for connections. I posted a question related to a specific error some of our MySQL customers were seeing that was related to character sets over here: fogbugz.stackexchange.com/questions/2156/… – db♦ May 24 2010 at 18:34

Does FogBugz 7 on MySQL handle non-latin characters correctly?

2 Answers