Re: Downgrade from 4.1.9 to 3.23.52
Yes, mysqldump seems to be the only solution for a downgrade.
I tried hard to reinstall MySQL 3 and directly use the tables from MySQL 4.1, but that didn't work.
Every time when a 'alter table' or 'create table' command is executed on MySQL 4.1, it modifies/creates the .frm-file in the MySQL 4.1 specific format, which cannot be read with MySQL 3.
If the .frm files have not been modified yet, we were able to use the same tables in MySQL 3 without conversion.
With 'show table status' we recognized, the tables having 'Version' set to 7 are unmodified and usable in MySQL 3. The ones that have 'Version' set to 9 are modified and have the new MySQL 4.1 specific .frm files.
I think the best way is to pipe the output from mysqldump to a script that splits the content into several files of < 2GB filesize.
Subject
Written By
Posted
February 14, 2005 07:00AM
February 15, 2005 02:12PM
Re: Downgrade from 4.1.9 to 3.23.52
February 17, 2005 07:19AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.