Sunday, January 6, 2013

Re: OperationalError: (2003, "Can't connect to MySQL server on 'localhost' (10061)")

On Sun, 6 Jan 2013 02:42:21 -0800 (PST), ANKIT BAGARIA
<mr.bagaria.24@gmail.com> declaimed the following in
gmane.comp.python.django.user:

>
> DATABASES = {
> 'default': {
> 'ENGINE': 'django.db.backends.mysql', # Add 'postgresql_psycopg2',
> 'mysql', 'sqlite3' or 'oracle'.
> 'NAME': 'django', # Or path to database file
> if using sqlite3.
> 'USER': 'name', # Not used with sqlite3.
> 'PASSWORD': 'pass', # Not used with sqlite3.
> 'HOST': '/var/run/mysql', # Set to empty string for
> localhost. Not used with sqlite3.

This wants the HOST machine on which the server runs -- NOT the path
to the server executable (actually, on my Windows box, "mysql" is the
interactive query shell, the server is "mysqld-something")
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment