migration from mysql 3.2.23 to 4.1.13

[Miroslav Lachman]

Don't forget to repair all tables /databases befor dump.
I recommend you to convert ISAM tables to MyISAM before dump. (but do it 
on backup copy of data, not on original)
Dump databases by newer mysqldump.
If you are using non latin1 charset, maybe you will have some troubles 
after importing dump into 4.1.
Do not blindly dump and reimport mysql users (table `user` from database 
`mysql`) because 4.1 has different structure and using different 
passwords. Manualy recreate all accounts instead.

Ruben Bloemgarten wrote:
> Hi Mario,
> The dump was done on 3.23. I'll give 4.1 a try on that machine, sounds like
> a nice hack though,using mysqldump 4.1 on a 3.23 database. Thanks for the
> tip.
> 
> Ruben 
> 
> -----Original Message-----
> From: mario [mailto:mario at schmut.com] 
> Sent: August 19, 2005 8:37 PM
> To: ruben at bloemgarten.demon.nl
> Cc: james at jpri.com; freebsd-isp at freebsd.org
> Subject: RE: migration from mysql 3.2.23 to 4.1.13
> 
> So, Ruben Bloemgarten wrote:
> 
>>Hi James,
>>
>>That was the first thing I tried, unfortunately that does not work as
>>the way 3.23 deals with ISAM is different to 4.1 and so it spits out
>>errors when it runs into unrecognizable syntax. If you have managed to
>>use mysqldump for a migration I would very much appreciate hearing about
>>it as it would simplify things conisderably.
> 
> 
> was this using mysldump 3.23 or 4.1? they produce different results and i
> found one to work and the other not. i don't remember which did what but
> just try the version you haven't yet.
> 
> then there is also
> http://dev.mysql.com/doc/mysql/en/upgrading-from-3-23.html
> and then
> http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html
> 
> looking at the docs, it seems, you need to do a bit more than just a dump.
> 
> hope this helps. i remember going from 4.0 to 4.1 was already fun.
> 
> 
> mario;>
> 
> 
> 
> 
>