Hi all,

I am planning to upgrade from 4.0.13 to 4.1.2 because my department will
need the subquery feature very soon, but the db server I am upgrading is a
live production server, and unfortunately we don't have the resources for a
testing machine to test things out. :(
So I would like to ask those who have upgraded from 4.0 to 4.1.....what else
should I pay attention to in addition to those mentioned in the manual.?

I am asking this because some time before when I have access to a
development machine, I tried to use some of the data from the current mysql
server and ran 4.1 on it, and I remember the following problems occured:
1) some versions of mysql4.0 client did not work well with 4.1
2) charset (or could it be collation ? I am not sure) was a big problem: I
remember we get 'You have an error in your SQL ...' when we issue queries,
and the solution was something like CONVERT('xxx' using latin1).
3) We have several databases containing different character sets (at least
utf8, big5 and plain ascii), and the 'character set problem' must be either
solved transparently or perhaps change some configuration directives on the
mysql server side but not to the applications.
4) If the default character set was set to big5, utf8 tables would have
problem. (?)
5) It was much slower than 4.0 at that time, I remember it consumed a lot
more cpu compared to 4.0.
6) Perhaps some other problems occured as well, but I just can't recall
them.

Sorry but I really don't remember when did I tested out 4.1, probably a year
ago or so (I think 4.0 was in alpha or beta stage at that time). So perhaps
things might have changed a lot. As I have no easy way to test out 4.1 with
the live db data, could anyone give me some hints on doing this? I would
like to have the upgrade go very smooth..

Thanks :D

P.S.: In the past few years mysql really did help us to solve a lot of
problems, and I would like to say thanks to all mysql developers!! :)

Cheers,
mc.



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to