Recent changes to bugs

connect_timeout parameter for connect on Windows

2017-04-08T16:43:47.206000Z

Using version 1.2.5 on Windows. The connect_timeout parameter for connect function does not work. It works fine on Linux.

#331 SELECT IN a list with only one element

2017-03-29T11:31:55.145000Z

A correct solution would be

if isinstance(args, dict):
query = query % {key: db.literal(item) for key, item in args.iteritems()}
elif isinstance(args, tupel):
query = query % tuple([db.literal(item) for item in args])
else:
query % db.literal(args)

#331 SELECT IN a list with only one element

2017-03-29T10:21:34.872000Z

This patch breaks stuff that worked with the previous version of mysql-python

eg.

cursor.execute("SELECT %s ...), (aString))

TypeError: not all arguments converted during string formatting

cursor.execute("SELECT %s ...), aString)

TypeError: not all arguments converted during string formatting

installation of windows version failed

2016-11-07T09:01:10.295000Z

Installation of MySQL-python-1.2.4b4.win32-py2.7.exe failed if python cannot be found. Actually it was installed in some other folders than program files/program files(x86). Error message: Python version 2.7 required, which was not found in the registry.

List of strings as parameters are double-quoted

2015-04-13T16:24:18.153000Z

When using list of strings as placeholders in cur.execute(), these get double-quoted (and thus never match/etc.):

scfc@tools-bastion-01:~$ dpkg-query -l python-mysqldb; python
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                              Version               Architektur           Beschreibung
+++-=================================-=====================-=====================-=======================================================================
ii  python-mysqldb                    1.2.3-2ubuntu1        amd64                 Python interface to MySQL
Python 2.7.6 (default, Mar 22 2014, 22:59:56) 
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import MySQLdb
>>> MySQLdb.version_info
(1, 2, 3, 'final', 0)
>>> con = MySQLdb.connect(host='tools.labsdb', db='toollabs_p', read_default_file='~/replica.my.cnf')
>>> cur = con.cursor()
>>> cur.execute('SELECT * FROM users WHERE name = %s', ('single string', ))
0L
>>> repr(cur._executed)
'"SELECT * FROM users WHERE name = \'single string\'"'
>>> cur.execute('SELECT * FROM users WHERE name IN %s', (('array', 'of', 'strings'), ))
0L
>>> repr(cur._executed)
'\'SELECT * FROM users WHERE name IN ("\\\'array\\\'", "\\\'of\\\'", "\\\'strings\\\'")\''
>>> 
scfc@tools-bastion-01:~$

LOAD DATA LOCAL query causes segfault in multi-threaded program

2014-12-23T19:38:10.181000Z

The following program gives a segfault:

import threading, _mysql

def run_load(conn):
    conn.query("LOAD DATA LOCAL INFILE '/tmp/a.txt' INTO TABLE test.x FIELDS TERMINATED BY ','")

if __name__ == '__main__':
    conn = _mysql.connect(host='127.0.0.1', user='root', db='', passwd='', local_infile = 1)
    t = threading.Thread(target=run_load, args=(conn,))
    t.start()
    t.join()

It appears that the problem is that mysql_thread_init() is not called in the new thread. Would it be possible to provide a function in _mysql that exposes mysql_thread_init()?

Segmentation fault under PyPy when performing concurrent queries with Twisted

2014-07-30T20:20:53.508000Z

Not sure whether this ticket tracker or the github tracker is more actively maintained, but here's the full information on the error and how to reproduce: https://github.com/farcepest/MySQLdb1/issues/79

#336 Wrong exception type generated

2014-07-26T14:23:01.384000Z

Github pull request:
https://github.com/farcepest/MySQLdb1/pull/78

Wrong exception type generated

2014-07-23T15:09:31.474000Z

According to the Python DB API 2.0 (http://legacy.python.org/dev/peps/pep-0249/#integrityerror), an IntegrityError should be raised when a required (NOT NULL) parameter is missing, but instead an OperationalError is raised.

Tested with mysql-python 1.2.3.

import MySQLdb
import MySQLdb.cursors

db = MySQLdb.connect(host="localhost", user="root", db="test", sql_mode="traditional")
db.autocommit(False)
cur = db.cursor()

cur.execute("DROP TABLE IF EXISTS `test`")
cur.execute("CREATE TABLE `test` (`integer` bigint(20) NOT NULL, `desc` varchar(255) NOT NULL)")
db.commit()
cur.execute("INSERT INTO `test` (`integer`) VALUES (%s)", (1, ))
db.commit()

$ python /tmp/test.py 
Traceback (most recent call last):
  File "/tmp/test.py", line 12, in <module>
    cur.execute("INSERT INTO `test` (`integer`) VALUES (%s)", (1, ))
  File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1364, "Field 'desc' doesn't have a default value")

#334 _mysql.so: undefined symbol: __gxx_personality_v0

2014-04-22T23:04:49.161000Z

Confirming this bug exists on Solaris as well, and that this patch resolved it.