Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In order just to get MySQL working again (I haven't yet looked at startup), there is no need to reinstall . I've got my copy working by doing the following:</p> <p>What you need to do is this:</p> <p><code>sudo ln -s /usr/local/mysql-5.0.51a-osx10.5-x86_64 /usr/local/mysql</code></p> <p>This creates a symbolic link from the /usr/local/mysql directory to the location where MySQL is. This is critical, because unless you carefully backed up all your databases with mysqldump before running the Leopard upgrade, that's where all your data lives - and restoring it simply from a whole-hard-drive backup is going to be hard.</p> <p>Now you can go to the right directory and start up mysql:</p> <p><code> cd /usr/local/mysql-5.0.51a-osx10.5-x86_64</p> <p>sudo ./bin/mysqld_safe</code></p> <p>You can now do the usual CTRL-Z to get back to the shell. To make sure mysqld is running, type: </p> <p><code>sudo ps -A|grep mysql</code></p> <p>I got something like this:</p> <p><code> 1220 ttys000 0:00.02 /bin/sh ./bin/mysqld_safe<br/> 1240 ttys000 0:00.39 /usr/local/mysql-5.0.51a-osx10.5-x86_64/bin/mysqld --basedir=/usr/local/mysql-5.0.51a-osx10.5-x86_64 --datadir=/usr/local/mysql-5.0.51a-osx10.5-x86_64/data --user=mysql --pid-file=/usr/local/mysql-5.0.51a-osx10.5-x86_64/data/dkmac-2.home.pid --port=3306 --socket=/tmp/mysql.soc</code></p> <p>My copy of mysql now seems to work fine. At the very least, it's good enough to run mysqldump on all my databases, so that if I need to upgrade mysql by other means and dump my data directory, I'm still in good shape.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload