I recently upgraded from 3.23.58 -> 4.1.20 without any hickups.
I simply dumped my databases with mysqldump on the 3.23.58 installation
and imported them again from inside the mysql client by using the
"source" command.
Dan Trainor wrote:
Hi -
I know we've rolled this around the list a few times, but I was
wondering if there's been any real development on the subject lately. I
know half of you are saying "Forget it... go with a newer version and
get over it", and I'd really really like to, but i have a lot of data
store under 3.23.x.
The documentation says that you must follow 3 -> 4.0 -> 4.1 -> 5.0 ...
..., and that's just what I'm about to do.
I guess what I'm looking for here is some advice from people who have
done it. If there's not an all-in-one silly stupid way to upgrade the
data in this manner (i.e. with one fell swoop of some handy dandy
application), would someone on an RPM-based system simply upgrade RPMs
in sequential order as indicated, and hope that the data follows? Is
this probably one of the more successful ways of doing this?
I'm still exploring my options, but I think that's what I'm going to end
up going with here - one step at a time.
If you guys wouldn't mind terribly talking about this for a few more
posts, I (and hopefully others) would greatly appreciate it.
Thanks for the time
-dant
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
