Recent changes to bugs

#289 utf8_bin collation will not convert to Unicode strings

Philipp Spitzer — Thu, 16 May 2013 20:17:05 -0000

MySQL-python 1.2.4 seemed to fix this issue. The column mentioned in the previous post is returned as UnicodeType now when using use_unicode=True in the connection string.
Thanks for fixing this.

#332 Memory leak with SSCursor (even when use_unicde=False)

Colin Morris — Mon, 06 May 2013 17:47:13 -0000

It seems I can't edit my ticket? Weird. Anyways, I should have mentioned, I'm using version 1.2.3c1.

Memory leak with SSCursor (even when use_unicde=False)

Colin Morris — Mon, 06 May 2013 17:44:56 -0000

conn = MySQLdb.connect(..., use_unicode=False, cursorclass=MySQLdb.cursors.SSCursor)
cur = conn.cursor()
cur.execute('select * from reallybigtable;')
print cur.fetchone()
cur.close()
conn.close()

The row is printed immediately, but rather than the program ending, it hangs, and python's memory goes up and up (it quickly grows above 1 GB). Sending a keyboard interrupt does nothing - I have to kill the process.

As far as I know, this is a separate issue from the memory leaks described in [#319] and [#265].

SELECT IN a list with only one element

T.L. — Tue, 23 Apr 2013 12:08:20 -0000

Hi,

I found a bug when running this bit of code in a Python console (Python 2.7.3). The point here is that I want to be able to select "in" a list, even when said list has only one element.

import MySQLdb

db = MySQLdb.connect({user: %%%, passwd: %%%; db: %%%, host: %%%, port: %%%})
cursor = db.cursor()
query = """SELECT 1 in %s"""

list_one = [1]
list_two = [1, 2]

try:
    cursor.execute(query, (list_one,))
    print "Query ok with %s." % list_one
except Exception as e:
    print "Query not ok with %s with exception %s." % (list_one, str(e))

try:
    cursor.execute(query, (list_two,))
    print "Query ok with %s." % list_two
except Exception as e:
    print "Query not ok with %s with exception %s." % (list_two, str(e))

A fix for this would be in cursor.py (line 159)

current:

query = query % db.literal(args)

fix:

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

Or am I missing a possible alternative syntax ?

Thanks a lot for your time!

#325 Datetime fields with microsecond shows as None

Zmicier Zaleznicenka — Thu, 28 Mar 2013 16:22:04 -0000

Also, if talking about these ms issues, while Time_Or_None() parses microseconds, rounding errors may appear. Instead, I suggest to use string methods.

This happens now:

>>> s='50.991'
>>> s = float(s)
>>> int(s)
50
>>>int(math.modf(s)[0]*1000000)
990999

This is what I think it should be:

>>> s='50.991'
>>> s,ms = s.split('.')
>>> int(s)
50
>>> int(ms.ljust(6,'0'))
991000

#325 Datetime fields with microsecond shows as None

Dmitry T. — Thu, 28 Mar 2013 15:52:56 -0000

I have tried in 1.2.4b4, result tuple have None if DateTime field contained microsecond.

Bug in DateTime_or_None() on times.py when func try to return value it can't split microsecond from time

return datetime(*[ int(x) for x in d.split('-')+t.split(':') ])

import datetime.datetime
d = '2013-03-28'
t = '11:11:11.000011'
datetime(*[ int(x) for x in d.split('-')+t.split(':') ])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: invalid literal for int() with base 10: '11.000011'

#325 Datetime fields with microsecond shows as None

Zmicier Zaleznicenka — Thu, 28 Mar 2013 14:49:52 -0000

The example works for the new versions of MySQLdb, but Date_Or_None() still parses datetimes with microseconds incorrectly, which leads to problems for clients using it directly (see i.e. https://code.djangoproject.com/ticket/19716). If it is possible, please make changes to Date_Or_None().

Add support for MySQL 5.5+

Gili Tzabari — Mon, 28 Jan 2013 00:32:48 -0000

MySQLdb-1.2.4 under Windows 7, 64-bit. When attempting to install MySQLdb-1.2.4 against MySQL 5.5 or higher I run into this bug:

http://stackoverflow.com/q/1972259/14731 (this isn't my question but I run into the same problem).

If you read on to http://stackoverflow.com/a/5685209/14731 you will see a simple fix. Can you please fold this into official MySQLdb releases?

#329 Provide a way of allowing autocommit

Jon Ribbens — Mon, 07 Jan 2013 14:13:09 -0000

The change appears to be deliberate, and is documented. It means that applications that have been working fine for many years with MySQL and mysql-python will suddenly stop working (in a way that may well be very hard to consistently repeat or diagnose). Personally I regard this as a bug in MySQL 5.5 but I don't expect they will agree.

#329 Provide a way of allowing autocommit

Andy Dustman — Mon, 07 Jan 2013 14:09:10 -0000

Found: http://bugs.mysql.com/bug.php?id=61391