manage.py dbshell fails to launch mysql for unix socket

[elyon001@…]

settings.py

database_engine = 'mysql'

database_host = '/var/lib/mysql/mysql.sock'

other fields omitted for this ticket.

python manage.py dbshell

ERROR 2005 (HY000): Unknown MySQL server host '/var/lib/mysql/mysql.sock' (1)

mysql -u root -h /var/lib/mysql/mysql.sock

ERROR 2005 (HY000): Unknown MySQL server host '/var/lib/mysql/mysql.sock' (1)

The socket file for connection is specified with the -S option of mysql executable

django is able to connect to the database normally and created my tables via syncdb, admin app can see my tables.

>>> import django


>>> django.VERSION

(1, 1, 1, 'final', 0)


>>> print sys.version

2.4.3 (#1, Sep  3 2009, 15:37:12) 
[GCC 4.1.2 20080704 (Red Hat 4.1.2-46)]

[Simon Law]

Here's a simple patch that works for me. Socket detection should probably be better than just testing whether '/' is in the path.

[Eric Holscher]

Seems like this could use a regression test, so that we make sure this continues to work in the future.

[Jacob]

I'm not sure I like this "magic switch on /" behavior. Are there any circumstances in which a network host could contain a /? If so, we need a different patch. Or just punt it: dbshell's a convenience, that's all.

[Simon Law]

jacob: ​http://tools.ietf.org/html/rfc3986#section-3.2.2 has the relevant information on host names. Neither IP addresses nor DNS registered names can have slashes in them.

[Russell Keith-Magee]

Not critical for 1.2.

[Russell Keith-Magee]

(In [13663]) [1.2.X] Fixed #12343 -- Added support for connection-by-socket to MySQL using the dbshell management command. Thanks to elyon001@… for the report, and sfllaw for the patch.

Backport of r13660 from trunk.

[Jacob]

Milestone 1.3 deleted