New Linux Server Guide

[bufferofnewbies]

I used the ax_peq15.rar,
not sure if you changed that version or not w/o a numeric change. If so, I will reload and retry (at least after i wake up.. been up all night now haha)

[Angelox]

Here's some points of interest from the MySql site;
Taken from here
http://dev.mysql.com/tech-resources/...1/unicode.html

Migrating from 4.0 to 4.1

If you have been using MySQL 4.0 as I outlined above, storing UTF-8 data in string columns regardless of the default server character set, one of the things you will want to do after upgrading to MySQL 4.1 is actually let the server know the true character set of those columns. But if you simply do an ALTER TABLE myTable MODIFY myColumn VARCHAR(255) CHARACTER SET utf8, the server will try to convert the data in the myColumn column from the server default character set to UTF-8. You need to do a two-step conversion to avoid this:

ALTER TABLE myTable MODIFY myColumn BINARY(255);
ALTER TABLE myTable MODIFY myColumn VARCHAR(255) CHARACTER SET utf8;

If you have multiple columns in the same table, you should do each step for all of the columns at the same time, to avoid having the entire table rebuilt for each step of converting each column. The "Converting 4.0 Character Columns to 4.1 Format" section of the manual provides an example of that.

If you were already using a specific server character set with MySQL 4.0, you can see how those character sets were mapped to the new character sets and collations in MySQL 4.1 in the "4.0 Character Sets and Corresponding 4.1 Character Set/Collation Pairs" section of the manual.