I reconfigured MySQL to allow local network connections, and
now MySQLdb works over TCP. It doesn't seem to be able to use
Windows 7 named pipes, although the "mysql" command line client can.
There may be a bug. This wouldn't be noticed unless MySQL
was configured without network connections, which is rare. I set
up MySQL that way on a development machine with a local MySQL instance.
John Nagle
On 6/11/2010 9:32 AM, John Nagle wrote:
On 6/10/2010 11:58 PM, Dennis Lee Bieber wrote:
On Thu, 10 Jun 2010 14:15:21 -0700, John Nagle<na...@animats.com>
declaimed the following in gmane.comp.python.general:
MySQL is configured for connections over named pipes only; it's
not running as a TCP server. Is MySQLdb trying to use TCP for a local
connection? The MySQLdb documentation says that connections to
"localhost" on Windows will be made over named pipes. Does that
not work?
I wouldn't be a tad surprised if M$ Win7 has implemented some
security/privilege scheme on named pipes such that cross process/user
access is blocked.
The MySQL command line client can connect with the same privileges.
So that may not be the problem.
John Nagle
--
http://mail.python.org/mailman/listinfo/python-list
