Jazz Snob,
jazz_snob;10916547 wrote:Nothing? Its gotta say something, right, even if its just to complain the command was not recognized.
The general use: mysql -u <user> -h <host> -p <database> then it will prompt you for password. Typically I only use mysql at the command line to process an sql file ala:
mysql -u user -h host -p database < some_data_or_table_structures.sql
Well, it did say something, but that was a week or two ago, and I have forgotten what they may have been.
The problem, apparently, is that I had to type in the full path plus mysql to get it to work, like this...
/Applications/MAMP/Library/bin/mysql -uroot -p
Before, I had navigated to...
/Applications/MAMP/Library/bin/
then typed...
mysql -uroot -p
and it didn't work, which makes no sense, considering these two scenarios seem like "six of one, a half-a-dozen of another" to me?!
Any way, I did it the second way and had luck.
Its useful to have aptitude for using the mysql client like when you have to access a remote system that doesn't have phpmyadmin or other way to get a "gui" interface of any kind. And its kinda cool...I have a thing for monochrome displays and blinking cursors that I can't explain.
Yes, I agree with you, and that is why I was trying to use the command line MysQL client versus phpMyAdmin.
Maybe I need to buy a "Dummies Guide to Unix" or something??
Amy