MySQL Connector/Python 2.2.2 m3 Development Release has been released
Balasubramanian Kandasamy <[email protected]> Thu, 1 Dec 2016 22:17:29 +0530
| Newsgroups | gmane.comp.db.mysql.announce,gmane.comp.db.mysql.general,gmane.comp.db.mysql.packagers |
|---|---|
| Message-ID | <[email protected]> |
Dear MySQL users,
MySQL Connector/Python 2.2.2 M3 is the third development release of the
MySQL Connector Python 2.2 series. This series adds support for the new
X DevAPI. The X DevAPI enables application developers to write code that
combines the strengths of the relational and document models using a
modern, NoSQL-like syntax that does not assume previous experience
writing traditional SQL.
To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information
about how the X DevAPI is implemented in MySQL Connector/Python, and its
usage, see http://dev.mysql.com/doc/dev/connector-python.
Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.
To download MySQL Connector/Python 2.2.2 M3, see the "Development
Releases" tab at http://dev.mysql.com/downloads/connector/python/
We are working on the github upload, it should be available soon.
Enjoy!
Changes in MySQL Connector/Python 2.2.2 (2016-12-01, Milestone 3)
* Functionality Added or Changed
* Bugs Fixed
Functionality Added or Changed
* If the MySQL server is configured to support secure
connections, Connector/Python now attempts to establish a
secure (encrypted) connection by default, falling back to
an unencrypted connection otherwise. This is behavior
similar to the --ssl-mode=PREFERRED option supported by
MySQL client programs.
The following TLS/SSL options have been implemented for
the mysqlx URI schema. All require Python 2.7.9 or
higher.
+ ssl-enable: This option enforces SSL connections. If
given, a connection attempt must be able to
establish a secure connection or the attempt fails.
+ ssl-ca: This option is used to verify the server
certificate.
+ ssl-cert, ssl-key: These options are used to pass
the client certificate and key, but the server
currently does not validate the client using these.
The ssl-enable parameter can be specified in a parameter
dictionary or URL, like this:
mysqlx.get_session({"user": "root", "host": "localhost", "port": 33060,
"password": "pass", "ssl-enable": True})
Or:
mysqlx.get_session("mysqlx://root:pass@localhost?ssl-enable")
The other parameters are used similarly. In a URL, path
name values should be given within parentheses; for
example, ssl-cert=(path_name). (Bug #24954646)
* There is now a standard API to create a table: Schema
objects have a create_table function. It throws an error
if the table exists.
* For any method that takes a value list of parameters for
its argument, there is now more flexibility with how the
parameters can be specified: Either as a value list or a
list of individual parameters. For example, these method
calls are the same:
Collection.add([{"a": 27}, {"a": 28}])
Collection.add({"a": 27}, {"a": 28})
* For Schema objects, get_view, create_view, alter_view,
and drop_view functions were added to support retrieval,
create, alter, and drop operations on View objects.
* Unix domain socket files are now supported as a
connection transport. The socket file can be specified in
a parameter dictionary or URL, like this:
mysqlx.get_session({"user": "root", "password": "pass",
"socket": "/path/to/socket"})
Or:
mysqlx.get_session("mysqlx://user:pass@(/path/to/sock)/schema")
mysqlx.get_session("mysqlx://user:pass@/path%2Fto%2Fsock/schema")
mysqlx.get_session("mysqlx://user:pass@.%2Fpath%2Fto%2Fsock/schema")
mysqlx.get_session("mysqlx://user:pass@..%2Fpath%2Fto%2Fsock/schema")
Bugs Fixed
* For a user created with REQUIRE SSL, establishing an SSL
connection by specifying --ssl-key but not --ssl-ca or
--ssl-cert fails for standard MySQL client programs. The
same connection configuration was (improperly) permitted
in Connector/Python. (Bug #24953032)
* Connection failures due to an improper SSL CA resulted in
an uninformative error message. (Bug #24948054)
* Using a schema object to alter a view failed if the view
selected from a non-INFORMATION_SCHEMA table and it was
altered to select from an INFORMATION_SCHEMA table. (Bug
#24947078)
* schema.create_collection() with an empty collection name
threw an improper error. (Bug #24520850)
Documentation
--------------------
Online:http://dev.mysql.com/doc/connector-python/en/index.html
The source distribution includes the manual in various formats under
the docs/ folder.
Reporting Bugs
--------------------
We welcome and appreciate your feedback and bug reports:
http://bugs.mysql.com/
On Behalf of the MySQL/ORACLE RE Team,
Balasubramanian Kandasamy