[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] upgrading MySQL from 3.22.32 to 3.23.36 on Raq3
- Subject: RE: [cobalt-users] upgrading MySQL from 3.22.32 to 3.23.36 on Raq3
- From: "Clark E. Morgan" <prlhkr@xxxxxxxxxxxxx>
- Date: Wed Apr 25 07:43:22 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I'm trying to upgrade Mysql without losing my current databases.
> Unless I'm
> misunderstanding the details posted at http://pkg.nl.cobalt.com/, this can
> be done only if you're running Chili!asp 3.5.2. When I log into my asp
> server control panel, it states that I'm running 3.1.0.0.
>
> If my previous assumptions are correct, how do I upgrade to chili 3.5.2 (I
> can only find 3.6 which it states will not work with the update) so I can
> upgrade to Mysql 3.23.36
I can't speak to what's in the pkg file and how that has been setup; but I
installed a hand compile of MySQL 3.23.36 with complete preservation of my
existing data. I backed it off using mysqldump just in case; but did not
need it. The entire process took less than 30 minutes and I followed the
basic source install procedure supplemented with the caveats listed at:
http://www.mysql.com/doc/U/p/Upgrading-from-3.22.html
It's an old fashioned point of view; but notwithstanding Cobalt warranty
concerns, I believe a source compile is a better, safer and more effective
option than .pkg, .rpm or any other binary packaging format. The often
unwarranted assumptions binary distributions have to make about target
systems can be a serious source of problems, often with disastrous
consequences.
Clark Morgan