Found a work-around for the way MySQL treats TIME literals with
dates and/or fractional seconds.
Added a mutex into the cursor so that connections can be shared between
threads. threadsafety=2
I could easily make the cursors sharable as well (threadsafety=3) but
I hardly see the point. Even sharing connections is not a good idea,
because you don't get the benefit of multiple mysqld threads.
the connection, a mapping of MySQL types to Python functions may be passed
as the keyword argument conv. This is stored as the converter attribute
on the connection object, and may be modified, assigned, etc.
MySQLdb: Build full converter dictionary, pass along to _mysql when
creating a connection.
MySQL_doc: Fixed a minor documentation bug.
I got from mxODBC author Marc-Andre Lemburg, which revealed the leak in
the first place.
Added a connection.rollback() method that always raises an
OperationalError, since MySQL doesn't have transactions.
connection.commit() still succeeds without doing anything.
which makes MySQL field types to Python functions which perform the
conversion. All numeric types except DECIMAL are mapped into either
PyInt or PyLong, and the floating point types are mapped into PyFloat by
default. Types which are not represented in the dictionary are returned
as strings.
Modified MySQLdb to adjust type_conv so that the various date/time types
are returned as DateTime objects.
Bug: If you were to delete or assign type_conv, bad things would happen.
I haven't actually tried this, but it wouldn't be good. May add an extra
reference count to prevent this, haven't really decided.
