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

MySQL Connector/Python Release Notes  /  Changes in MySQL Connector/Python 1.1  /  Changes in MySQL Connector/Python 1.1.0 (2013-07-02, Alpha)

Changes in MySQL Connector/Python 1.1.0 (2013-07-02, Alpha)

Functionality Added or Changed

  • Incompatible Change: Python 2 code was changed to use new features introduced in Python 2.6 and 2.7. Some examples:

    • print() is used as a function, not a statement.

    • Exceptions are handled using the as keyword.

    • The in keyword is used instead of the has_key() dictionary method.

    This change means that MySQL Connector/Python 1.1 does not work with versions of Python older than 2.6. (WL #6509)

  • Connector/Python was updated with error information from MySQL 5.7.1. (Bug #16896702)

  • mysql.connector.__version__ and mysql.connector.__version_info__ now are available to provide MySQL Connector/Python version information in a more standard, Pythonic manner. (WL #6517)

  • MySQLConnection objects now support an in_transaction property that returns True or False to indicate whether a transaction is active for the connection. (WL #6574)

  • MySQLConnection objects now support a start_transaction() method to begin a transaction. This method accepts arguments indicating whether to use a consistent snapshot and which transaction isolation level to use:


    The default consistent_snapshot value is False. The default isolation_level value is None, and permitted values are 'READ UNCOMMITTED', 'READ COMMITTED', 'REPEATABLE READ', and 'SERIALIZABLE'. (WL #6573)

  • Connector/Python supports a new MySQLCursorPrepared class that enables execution of prepared SQL statements using the binary client/server protocol. For details, see cursor.MySQLCursorPrepared Class. (WL #6148)

Bugs Fixed

  • Relative imports were removed from Python 3 code. PEP-8 indicates that relative imports are discouraged. (Bug #16234372)