possibly same issue as http://forums.mysql.com/read.php?10,408161,408181#msg-408181
$ ./mysql -u root -proot --protocol=tcp --host=127.0.0.1
Warning: Using a password on the command line interface can be insecure.
> show databases;
[WAIT FOREVER AND NOTHING EVER HAPPENS]
> exit;
ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'exit' at line 1
[uhhhhhhhh what?]
Database
information_schema
mysql
performance_schema
phpmyadmin
temp
othertables
[!?!]
$ ./mysql -u root -proot --protocol=tcp --host=127.0.0.1
Warning: Using a password on the command line interface can be insecure.
> UPDATE blah blah blah;
[NOTHING EVER]
exit;
ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'exit' at line 1
[SO DID IT WORK????!!!!!!! WHAT THE!!!!!]
$ ./mysql -u root -proot --protocol=tcp --host=127.0.0.1
Warning: Using a password on the command line interface can be insecure.
> select * from blah blah blah
[NOTHING EVER]
> exit;
ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'exit' at line 1
[UHHH so did it select zero lines???? one two..... !!!!!!!]
so sometimes it responds... but only when you don't really care what the response is and only after mysql decides to spontaneously combust...............
PHP couldn't be compiled on my system so I am now using EasyPHP (which I assume is irrelevant).
Any ideas... it's as if though mysql can't communicate with my console correctly... does mysql use non-standard terminal emulation???? it works fine on a CentOS server.
The commands appear to work, however not having a direct line of sight to the actual contents of the database is a MASSIVE hindrance to ANY debugging issues.
MySQL is almost completely incompatible with Cygwin's console.
I don't know who is at fault for using non-standard terminal behavior... (but I tend to assume MySql is at fault given that it should only be basic input and output, and most other native programs work well enough)
In order to use native MySQL on Windows you MUST use the windows Command Prompt.