2013.02.26

MySQL

MySQL Connector/Python 1.0.9がリリースされました

オリジナル版:http://lists.mysql.com/announce/813

>MySQL Connector/Python v1.0.9はMySQL用のピュアPythonデータベースドライバの1.0プロダクションリリースの新バージョンです。

MySQL Connector Pythonのバージョン1.0はMySQL 5.5以上と互換性を持ちますが、それ以前のバージョンでも動作します(バージョン4.1以上)。Python v2.6とPython v3.1以上でサポートされます。Python v2.4とv2.5で動作することは知られていますが、公式にはサポートされません。

MySQL Connector/Python v1.0.9はhttp://dev.mysql.com/downloads/connector/python/#downloadsからダウンロード可能です。

MySQL Connector/Python v1.0での変更の要約は下記にリストアップされています。より完全な変更のリストは配布物内の変更履歴を確認してください。

Changes in MySQL Connector/Python v1.0.8
----------------------------------------
Changes in MySQL Connector/Python v1.0.9
----------------------------------------

  Functionality Added or Changed

      * Previously, when setting up an SSL connection, the developer
        had to set the ClientFlag.SSL explicitly in the client_flags
        argument of the mysql.connector.connect() function call. Now,
        whenever SSL arguments are specified, the client flag is set
        automatically. This change makes the SSL behavior of
        Connector/Python more consistent with other MySQL connectors.
        (Bug #16217667, Bug #68172)

  Bugs Fixed

      * The DistUtils command was not copying version.py into the
        build directory, so that the build/lib directory could not be
        used for development without manually copying version.py. (Bug
        #16236136)

      * Passing string parameters to a stored procedure resulted in
        extra quotes being included in the value. This was caused by
        the conversion from Python to MySQL data types being applied
        two times. We now only convert once, and pass the values
        correctly.
        MySQLCursor.callproc() now also raises a ValueError when the
        type of an argument is incorrect. (Bug #16217743, Bug #68066)

      * Fixed IPv6 for older Microsoft Windows versions. Also improved
        the associated code for all operating systems: we now use
        socket.getaddrinfo() instead of inet_pton() to check whether
        we are connecting using IPv4 or IPv6.
        A new connection option force_ipv6 has been introduced. When
        set to True, IPv6 will be used when an address resolves to
        both IPv4 and IPv6. Otherwise, IPv4 is favored. (Bug
        #16209119)