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

MySQL Connector/Python Release Notes  /  Changes in MySQL Connector/Python 2.2  /  Changes in MySQL Connector/Python 2.2.3 (2017-03-22, Development Milestone)

Changes in MySQL Connector/Python 2.2.3 (2017-03-22, Development Milestone)

MySQL Connectors and other MySQL client tools and applications now synchronize the first digit of their version number with the (highest) MySQL server version they support. For example, MySQL Connector/Python 8.0.12 would be designed to support all features of MySQL server version 8 (or lower). This change makes it easy and intuitive to decide which client version to use for which server version.

Connector/Python 2.2.3 was the final release to use the old numbering. It is the predecessor to Connector/Python 8.0.4.

Functionality Added or Changed

  • The pure Python implemention of Protobuf has been replaced by a C++ extension. This enables Connector/Python to support Python 2 and 3 as well as Protobuf 2 and 3. (Bug #25209469, WL #10452)

  • Connector/Python now supports IPv6 target hosts in X DevAPI connection strings. (WL #10081)

Bugs Fixed

  • The defined_as(statement) method used to create views did not permit a SelectStatement object argument (generated by (Bug #25614860)

  • The SelectStatement object returned by failed to provide the order_by() method. (Bug #25519251)

  • import mysqlx caused an error with Python 2.6 on Solaris and EL6 platforms. (Bug #24578507)

  • The error message for get_session() failure was incorrect. (Bug #23636962)

  • The Collection.find() method failed to work with the LIKE operator or aggregate functions.

    The Collection.find() method failed to work with several operators. Support was added for these operators:

    • Nullary Operators:

    • Unary Operators:

      !, NOT, +, -, ~
    • Binary Operators:

      AND, &&, OR, ||, XOR, <>, ^
    • Ternary Operators:


    In addition, arrow notation to access JSON columns is now functional (for example, schema.table.column->'$.document field'). (Bug #23567724, Bug #23568207, Bug #25436568, Bug #84585)