Topic: Upgrading to v.6 - what to do with mySQL databases?

[stewart midwinter]

I read that when moving up to v.6, it's best to do a fresh install. So, what to do with any mySQL databases?  I've tried doing an SQL export using phpMyAdmin (using the rpm from contribs.org) to a flat file, which I can then archive off the server, but I have a concern.  When I view the flat file with a text editor, the contents of some of the fields look like they're in hex code or something: they appear as long strings of characters that are illegible to humans.   Does that seem right?

thanks,
Stewart

[Will]

Login into mysql and dump the data and structures of your database
Put the resulting files somwhere safe and your ready to rock.

You normally won't always be able to read the everything in the resulting file if your database holds more than just text.

[Charlie Brady]

stewart midwinter wrote:

> I read that when moving up to v.6, it's best to do a fresh
> install.

Unless you are updating from pre 5.5, there's no need. Even for pre 5.5, update should work, as long as you apply a few workarounds which you can find documented here.

> So, what to do with any mySQL databases?

mysql databases are dumped and included in any backup you do. IIRC, they are automatically restored as well (they are for webmail preferences, which are the only dbs in the standard product).

Charlie