Documentation Home
MySQL Connector/Python Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 224.3Kb
PDF (A4) - 225.1Kb


MySQL Connector/Python Release Notes  /  Changes in MySQL Connector/Python 2.1  /  Changes in MySQL Connector/Python 2.1.2 (2015-04-30, Beta)

Changes in MySQL Connector/Python 2.1.2 (2015-04-30, Beta)

Functionality Added or Changed

  • Previously, connections from Connector/Python to Fabric were always made using the XML-RPC protocol. It is now possible to connect using the MySQL client/server protocol. To specify the protocol, use the protocol value in the fabric dictionary argument for the connect() method. Permitted protocol values are xmlrpc (the default) and mysql. With mysql, the default port becomes 32275, although that can be changed with an explicit port value.

Bugs Fixed

  • Connector/Python could raise an AttributeError exception for Fabric connections with MySQL Utilities 1.5.4 or 1.6.1. (Bug #20834643)

  • The setup.py install command did not retain the value provided by the --install-lib option. (Bug #20217174)

  • Encoding failure could occur for prepared cursors with UTF-8 statement parameters. (Bug #75542, Bug #20407036)

  • The Connector/Python version checker for MySQL did not handle nonnumeric suffixes. During the build process, if the --with-mysql-api option was given, the check failed for installed versions of MySQL such as 5.7.6-m16. (Bug #75520, Bug #20365619)

  • Values of the SET data type were not translated correctly if empty. (Bug #75402, Bug #20301989)

  • HASH sharding for Fabric failed. (Bug #75287, Bug #20324089)

  • Queries that produced a large result could result in an IndexError: bytearray index out of range exception. (Bug #74933, Bug #20462427)

  • The Django back end was creating excessive connections (immediately when each DatabaseWrapper object was created rather than waiting until the object actually needed the connection.) (Bug #74696, Bug #19972427)

  • Error messages containing non-ASCII characters caused an exception to be raised. (Bug #74345, Bug #19803702)

  • The Django back end sometimes failed to properly convert SafeText objects, which then appeared in queries. (Bug #74336, Bug #20106629)

  • When using the callproc() cursor method, warnings generated by statements executed within the procedure or generated by the procedure itself were not available to the client. (Bug #74252, Bug #19777815)

  • Connection pooling did not work when using MySQL Fabric. (Bug #73445, Bug #19331658)