For one, version 6.0 was canned as part of the transition to “more frequent and timely releases of the MySQL Server.” Version 7 was reserved for the clustering version of MySQL.

We started development with the MySQL 4.1.1 release and noticed a few complex queries where the ordering did not work as expected; we were forced to rewrite the queries or break a single query ...

It seems that MySQL 4.1 isn't mature enough to handle the complexities of UTF-8. It would seem to me (having used Oracle) that specifying UTF-8 as the database encoding would take care everything.

OK. So, I inherited an ASP 3.0 web app that I just recently realized has a character encoding problem. Long story short, the data that users are submitting has started to become riddled with ...