On 9/1/2010 1:00 PM, Aniruddha wrote:
On Tuesday 31 August 2010 20:30:55 Mick wrote:
But this is apparently not the proper way, because after
restarting the server, apache does not show my web-page
reporting there is no such a database. I checked it with
phpmyadmin, and really, there is absolutely no database
in mysql!
I quickly restored backup version which I have done just
before trying mysql-update, so my web-site is up and running.
Now I would like to update mysql the right way, I but do not
know how to do it...
Hi Jarry,
Some years ago I ran into some similar problem, I can't recall exactly
what. Lost in folklore (wiki?) were some instructions to first stop mysql
before you update it and I have been following them since.
I stop apach& mysql, run the update, dispatch-conf and then restart them
both. Haven't had problems since.
There may be a better way for doing this - in which case others who know
better will hopefully chime in.
I'm curious as well. Imo it shouldn't be necessary to stop mysql server for
each update.
I did in place upgrades from 5.0.12 or so on up to 5.0.77 or so. You're
unlikely to have problems upgrading Mysql within 5.0.x. If you're moving
up to 5.1, I would definitely stop inserts into Mysql, dump mysql, stop
mysql, make a copy of /var/lib/mysql just in case, then upgrade to 5.1.
Mysql should be able to upgrade your database in place, but it might
not. If mysql-update doesn't work, importing a dumb is the most reliable
way to get your data into 5.1.
As other people have pointed out you'll need to revdep-rebuild or
preserve the older client libs.
kashani
