On Wed, Jan 04, 2006 at 09:35:16PM -0500, David Coe wrote:
> Thanks; yes, I see that my 'mysql' host and other system tables are
> .ISM and .ISD files; I assume that means ISAM.
Yep. Thats what I had.
> I was able to downgrade to 4.1, which I figured would be safe since
> the 5.0 server had never actually started; I'm going to stay there
> for now. If you'd like me to test a new upgrade path, I'll be happy
> to do that ; even if I were to lose all the mysql data, it would be
> no major loss.
The manual fix is to run "mysql_convert_table_format mysql" to
upgrade your "mysql" database to the MyISAM table format and
then the upgrade to 5.0 should go smoothly.
If you have any data at risk, run "mysqldump --opt
--all-databases" so you can recover your data if something
tragic happens.
Maintainers: perhaps the preinst should check for any
databases having .IS[MD] files and abort if they are found,
warning the user to run mysql_convert_table_format or possibly
running it for them before stopping and purging the old 4.1
server?
--
Caleb Epstein | bklyn . org |<Culus> Hhhmmmmmmmm <Culus> waterbeds for cows
cae at | Brooklyn Dust |<Culus> eleet <cas> Culus: why would a cow need
bklyn dot org | Bunny Mfg. |a waterbed? <Culus> cas: To be comfy warm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
