Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A fix for CocoaMySQL / MySQL 4.1 connection issues Apps
CocoaMySQL is a splendid (and free) graphical interface for MySQL databases. Unfortunately, connecting to a MySQL 4.1 server can be tricky. When I first tried, the only warning I got was 'connection failed' -- even though I was sure I provided all the correct information (host, user, password...). The problem is that MySQL, as of version 4.1, uses a new encryption algorithm to store its passwords. And CocoaMySQL (v 0.5) doesn't know how to deal with that. Users without a password have no trouble to connect, but we don't want to throw security overboard for a good interface, do we?

Luckily, MySQL 4.1 has a feature to preserve backward compatibility by using the "old" encryption for your passwords -- users with such password are able to connect via CocoaMySQL without any problem at all. Creating an "old" password is simple in the Terminal, using the MySQL command line interface:
 SET PASSWORD FOR 'mysql_username'  = OLD_PASSWORD('password');  
[robg adds: I haven't tested this one. I would think that an update to CocoaMySQL would take care of the problem. However, according to their webpage, it hasn't been updated since Fall of 2003, so I'm not sure how likely that is.]
    •    
  • Currently 1.00 / 5
  You rated: 1 / 5 (2 votes cast)
 
[20,620 views]  

A fix for CocoaMySQL / MySQL 4.1 connection issues | 12 comments | Create New Account
Click here to return to the 'A fix for CocoaMySQL / MySQL 4.1 connection issues' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: rael9 on Feb 15, '05 10:58:42AM
Or you can use the modified version of CocoaMySQL. It works fine with the new algorithm.

---
"Beer, the cause of, and solution to, all of life's problems." - Homer J. Simpson

[ Reply to This | # ]

A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: ppatoray on Feb 15, '05 08:37:30PM

It 'mostly' works fine, with a few exceptions. The console logging doesn't work for me, and every once in a while, it will seem to lose its connection as I switch database tables or switch from structure to content, but not that often, and I get a corresponding message in my console.log

2005-02-14 13:38:06.641 CocoaMySQL[13024] Error message is : Lost connection to MySQL server during query
2005-02-14 13:38:07.735 CocoaMySQL[13024] *** -[NSPlaceholderString initWithString:]: nil string (or other) argument

Unfortunately, there is no contact information available on this website for the author, so I haven't been able to email him.



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: MonkeyT on Feb 16, '05 01:20:12PM

I've had few problems with it, but very rarely, the interface itself locks up on me: Popups still display normally, but it won't refresh the window or switch tabs, particularly if I was viewing database contents. It's worse for very large datasets. Possibly a memory thing. I've found that sending the window to the Dock and enlarging it again brings it back to displaying properly.



[ Reply to This | # ]
same problem for navicat?
Authored by: jspivack on Feb 15, '05 11:17:19AM

Does anyone know if Navicat is having the same problem? I have been recently unable to connect to a remote MySQL server with either navicat or CocoaMySQL, although the site administrator assures me that my settings are OK. This might be the issue - but only if Navicat suffers from the same defect.



[ Reply to This | # ]
nope, must be something else
Authored by: jspivack on Feb 15, '05 02:41:36PM

l tried the "fixed" version mentioned above, and got the same results. I must have some other problem.



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: c8h10n4o2 on Feb 15, '05 02:17:45PM

I've had good luck with DBVisualizer. It is a Java App, cross-platform and no problems connecting with MySQL 4.1.

The "Free" version is available for download after providing some information about yourself.

Product Page - http://www.minq.se/products/dbvis/
Download Page - http://www.minq.se/products/dbvis/download.html



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: allanmarcus on Feb 15, '05 03:11:45PM

Another free solution (for personal use) is Aqua Data Studio.



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: ar on Feb 15, '05 07:41:37PM

Oh brilliant! I was having exactly this problem the other day, wondering why it wasn't working. Can't wait to try this solution out, thanks a bunch!



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: matx666 on Feb 15, '05 07:45:38PM

I had the worst time trying to get phpMyAdmin and the new mysql to talk to each other yesterday, until I called a friend who knows mysql and he said the password hashes between the two apps were not jiving. The problem started when we tried to change the password with phpMyAdmin and then nothing worked when we tried to log in to phpMyAdmin. Resolution occurred only when we used mysql to change the passwords, old-style. So all apps should be having this problem... what a headache! (thanks Durandal!)



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: wontz on Feb 15, '05 09:10:40PM

I write to author recently and he tell me that a new version is on the way... be patient ;-)



[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: iangrant on Mar 28, '06 03:13:51AM
http://cocoamysql.sourceforge.net/beta.php The CocoaMySQL 0.7b3 beta has fixed connection problems for me. I'm running Mac OS 10.4.5 and mysql 4.1. I use Your SQL for a while but really prefer the GUI of CocoaMySQL

[ Reply to This | # ]
A fix for CocoaMySQL / MySQL 4.1 connection issues
Authored by: rorysolomon on Mar 15, '07 11:22:03AM
Thanks for the info -- super informative. Your SQL didn't work for me though. But I just used the following instead:
update user set password = old_password('password') where user = 'username';
... maybe that will be helpful to someone else.

[ Reply to This | # ]