MySQL for Mac

Question

Level 1

0 points

MySQL for Mac

Hi all,

I run into an issue with upgrading MySQL. I am running Mac OS X v10.4.11 Server on a X-Server G5. The version of MySQL that came with the OS is Ver 14.7 Distrib 4.1.22, for apple-darwin8.0 (power pc). I went to the MySQL website and downloaded the newest community edition available for Mac. That version is 5.1.37. The download loaded in /usr/local. The version that comes with the OS is sitting in /var/mysql.
At command line when I use mysql -V it will display mysql 4.1.22, but when I log into mysql using mysql -u root, it show the new server version of 5.1.37. I have tried to migrate data from another server that using v5.1.37 and I get errors. It appears that while I show v5.1.37 when I log into the db, that it is actually 4.1.22. Any advice on this? TIA for your help.

G5 X-Serve, Mac OS X (10.4.11), MySQL 4.1.22 and 5.1.37

Posted on Aug 6, 2009 3:41 PM

Reply

Answer 1

Camelot

Level 9

58,575 points

Aug 7, 2009 12:06 PM in response to beekertx

It appears that while I show v5.1.37 when I log into the db, that it is actually 4.1.22

You are mis-reading what you're seeing.

At command line when I use mysql -V it will display mysql 4.1.22

When you run this command it is reporting the version of your MySQL client, not the server. Since you're not specifying which mysql client to use the OS is searching your $PATH and using the first one it finds - clearly the original OS installed version

when I log into mysql using mysql -u root, it show the new server version of 5.1.37.

When you log in, you're talking to the server, which is why you get the different version number. So now you're using MySQL client 4.1.22 with MySQL Server 5.1.37. That's OK, but clearly not what you expected.

. I have tried to migrate data from another server that using v5.1.37 and I get errors

Could you be at all specific about what errors you get. Knowing that would go a long way to answering your question (at least compared to working blind, which is what you're asking us to do).
You should also read the MySQL migration guide which talks about differences between 4.1.x and 5.1.x and how to migrate your data - you can't just open your existing database files and expect it to work.

Reply

Answer 2

beekertx Author

Level 1

0 points

Aug 10, 2009 7:51 AM in response to Camelot

Thank you for your response. As you requested, here are the errors I am getting when trying to migrate data. I seem to remember getting this before when I was trying to migrate data from an older version of MySQL to a newer, hence why I felt like I was not getting to the new Db at all. Here they are. Thank you again for your help.

spider:/ root# sudo mysqldump WebBB < WebBB.sql
-- MySQL dump 10.9
--
-- Host: localhost Database: WebBB
-- ------------------------------------------------------
-- Server version 5.1.37-log

/*!40101 SET @OLD CHARACTER_SET_CLIENT=@@CHARACTER_SETCLIENT */;
/*!40101 SET @OLD CHARACTER_SET_RESULTS=@@CHARACTER_SETRESULTS */;
/*!40101 SET @OLD COLLATION_CONNECTION=@@COLLATIONCONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD UNIQUE_CHECKS=@@UNIQUECHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD FOREIGN_KEY_CHECKS=@@FOREIGN_KEYCHECKS, FOREIGN KEYCHECKS=0 */;
/*!40101 SET @OLD SQL_MODE=@@SQLMODE, SQL MODE='NO_AUTO_VALUE_ONZERO' */;
/*!40111 SET @OLD SQL_NOTES=@@SQLNOTES, SQL_NOTES=0 */;

/*!40101 SET SQL MODE=@OLD_SQLMODE */;
/*!40014 SET FOREIGN KEY_CHECKS=@OLD_FOREIGN_KEYCHECKS */;
/*!40014 SET UNIQUE CHECKS=@OLD_UNIQUECHECKS */;
/*!40101 SET CHARACTER SET_CLIENT=@OLD_CHARACTER_SETCLIENT */;
/*!40101 SET CHARACTER SET_RESULTS=@OLD_CHARACTER_SETRESULTS */;
/*!40101 SET COLLATION CONNECTION=@OLD_COLLATIONCONNECTION */;
/*!40111 SET SQL NOTES=@OLD_SQLNOTES */;

spider:/ root#

Reply