MySQL Connector/C 6.1.10 GA has been released

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C has been
made available: MySQL Connector/C 6.1.10 GA. The MySQL Connector/C 6.1
implements the MySQL C API for connecting client applications to the
MySQL Server 5.5 or newer.

You can download the production release at:
http://dev.mysql.com/downloads/connector/c/6.1.html

MySQL Connector C (Commercial) will be available for download on the My
Oracle Support (MOS) website. This release will be available on
eDelivery (OSDC) in next month’s upload cycle.

Please see the documentation and the README file in the source distribution
for a detailed description of bugs that have been fixed.

Enjoy!

Changes in MySQL Connector/C 6.1.10 (2017-04-28, General
Availability)

Compilation Notes

* The Windows version of MySQL Connector/C Community is now
built using the dynamic C runtime libraries (that is,
with the /MD compiler option), with the following
implications for users:

+ Target hosts running Windows applications that use
MySQL Connector/C Community now need the Visual C++
Redistributable for Visual Studio 2015
(https://www.microsoft.com/en-us/download/details.aspx?id=48145)
installed on them.

+ Client applications on Windows that use MySQL
Connector/C Community should be compiled with the
/MD compiler option.

Security Notes

* The linked OpenSSL library for MySQL Connector/C 6.1
Commercial has been updated to version 1.0.2k. For a description
of issues fixed in this version, see
http://www.openssl.org/news/vulnerabilities.html. This change
does not affect the Oracle-produced MySQL Community build of
Connector/C, which uses the yaSSL library instead. (Bug
#25615447)

On behalf of the Oracle MySQL Release Engineering Team,
Nawaz Nazeer Ahamed

MySQL Connector/Python 2.2.3 m4 Development Release has been released

MySQL Connector/Python 2.2.3 M4 is the fourth 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 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.3 M4, see the “Development Releases” tab at http://dev.mysql.com/downloads/connector/python/

Enjoy!

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

Functionality Added or Changed

* Connector/Python now supports IPv6 target hosts in X DevAPI connection strings.

Bugs Fixed

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

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

* 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)

* 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, <>, ^, IS NOT, NOT REGEXP, NOT LIKE, CAST, NOT IN

+ Ternary Operators: NOT BETWEEN

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)

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,
Piotr Obrzut

MySQL Connector/C 6.1.9 GA has been released

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C has
been made available: MySQL Connector/C 6.1.9 GA. The MySQL
Connector/C provides a C API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/c/1.1.html

MySQL Connector C (Commercial) will be available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month’s upload cycle.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

======================================================================

Changes in MySQL Connector/C 6.1.9 (2017-01-10, General
Availability)

Security Notes

* OpenSSL is ending support for version 1.0.1 in December
2016; see
https://www.openssl.org/policies/releasestrat.html.
Consequently, Connector/C Commercial builds now use
version 1.0.2 rather than version 1.0.1, and the linked
OpenSSL library for the Connector/C Commercial has been
updated from version 1.0.1 to version 1.0.2j. For a
description of issues fixed in this version, see
https://www.openssl.org/news/vulnerabilities.html.
This change does not affect Oracle-produced MySQL
Community builds of Connector/C, which use the yaSSL
library instead. (Bug #24753384)

* A new MYSQL_OPT_TLS_VERSION option is available for the
mysql_options() C API function to indicate the protocols
permitted by the client for encrypted connections.
For more information, see mysql_options()
(http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html).
(Bug #22932026)

* A new MYSQL_OPT_SSL_MODE option is available for the
mysql_options() C API function to indicate the security
state to use for the connection to the server.
For more information, see mysql_options()
(http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html).
(Bug #22931973)

Functionality Added or Changed

* Previously, Connector/C permitted user names up to a
maximum of 16 characters. Connector/C now permits longer
user names (up to 32 characters) if the server does. (Bug
#22931954)

* Connector/C now includes support for the server GTID
session tracker, introduced in MySQL 5.7.6. This tracker
is exposed through the session_track_gtids system
variable. (Bug #21040741)

* Connector/C now includes support for additional ranges of
server errors, introduced in MySQL 5.7.6. (Bug #21040703)

On Behalf of the MySQL/ORACLE RE Team
Piotr Obrzut

MySQL Connector/Python 2.1.5 GA has been released

Dear MySQL users,

MySQL Connector/Python 2.1.5 GA is a third GA version of 2.1 release
series of the pure Python database driver for MySQL. It can be used for
production environments.

MySQL Connector/Python version 2.1.5 GA is compatible with MySQL Server
versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3
and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not
supported.

MySQL Connector/Python 2.1.5 is available for download from:

http://dev.mysql.com/downloads/connector/python/#downloads

The ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 2.1.5. For a more complete list of
changes, see below or online at:

http://dev.mysql.com/doc/relnotes/connector-python/en/

Enjoy!

Changes in MySQL Connector/Python 2.1.5 (2016-12-15, General
Availability)

Bugs Fixed

* Incorrect logic for handling EOF packets caused MySQL
Utilities replication to fail. (Bug #25111218)

* Using the C Extension, connection failure occurred when
the user name or password contained Unicode characters.
(Bug #21656282)

* For connections established using the use_pure=True
parameter, queries that returned more than 4096 columns
produced an InterfaceError. (Bug #21530841)

* Using Python 3.3, connection failure occurred if the
option_groups parameter named multiple groups. (Bug
#21530100)

* Using executemany() to execute an INSERT INTO … SELECT
statement produced an InterfaceError. (Bug #21477493)

* If a call to set_charset_collation() failed, the
character set became invalid rather than being unchanged.
(Bug #21476495)

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,
Piotr Obrzut

MySQL Connector/Python 2.2.2 m3 Development Release has been released

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/index.html. 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

MySQL Connector/Python 2.1.4 GA has been released

The MySQL Connector/Python Team is pleased to announce the newest MySQL Connector/Python 2.1.4, the second GA version of 2.1 release series of the pure Python database driver for MySQL.

This release includes a number of improvements for usability, stability and security.

Changes in MySQL Connector/Python 2.1.4 GA

Security Notes

The linked OpenSSL library for Connector/Python Commercial has been updated to version 1.0.1q. Issues fixed in the new OpenSSL version are described at http://www.openssl.org/news/vulnerabilities.html. This change does not affect Oracle-produced MySQL Community builds of Connector/Python, which use the yaSSL library instead.
The change also does not affect connections made using any pure Python implementation of Connector/Python, for which the version of OpenSSL used is whatever is installed on the system.

Bugs fixed

  • Connector/Python failed to establish connections using the cleartext client-side authentication plugin for accounts using the PAM server-side authentication plugin. Thanks to Daniël van Eeden for the patch. (Bug #22873551, Bug #80609)
  • A potential SQL injection vector was eliminated. (Bug #22529828)
  • Connections made using the C Extension failed when the ssl_ca parameter was given without ssl_cert and ssl_key. (Bug#21879914, Bug #79835, Bug #22494320)
  • For connections made with consume_results=True, consume_results was reset to False after callproc() execution failure. (Bug #21879859) References: This issue is a regression of: Bug #21492815.
  • In connections for which compress=True, LOAD DATA LOCAL INFILE statements produced “Packets out of error” errors. (Bug#21449996)
  • Attempts to insert Python ByteArray data into binary table columns failed. (Bug #77822, Bug #21498719)

Quick links

Documentation: http://dev.mysql.com/doc/connector-python/en/index.html
Release Notes: http://dev.mysql.com/doc/relnotes/connector-python/en/index.html
Downloads: http://dev.mysql.com/downloads/connector/python/#downloads
Feedback, bugs and feature requests: http://bugs.mysql.com
Forum: http://forums.mysql.com/list.php?50
On GitHub: https://github.com/oracle/mysql-connector-python

Thanks

Thank you all for your support and feedback!

On behalf of the MySQL Connector/Python Team.

MySQL for Excel 1.3.5 has been released

The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.5. This is a maintenance release for 1.3.x. It can be used for production environments.

MySQL for Excel is an application add-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as:

  • Importing MySQL data into Excel
  • Exporting Excel data directly into MySQL to a new or existing table
  • Editing MySQL data directly within Excel

MySQL for Excel is installed using the MySQL Installer for Windows which comes in 2 versions:

  • Full (150 MB) which includes a complete set of MySQL products with their binaries included in the download
  • Web (1.5 MB – a network install) which will just pull MySQL for Excel over the web and install it when run.

You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/.

MySQL for Excel can also be downloaded by using the product standalone installer found at this link http://dev.mysql.com/downloads/windows/excel/

 

Changes in MySQL for Excel 1.3.5 (2015-10-23)

This section documents all changes and bug fixes applied to MySQL for Excel since the release of 1.3.5. Several new features were added to the 1.3.x branch, for more information see What Is New In MySQL for Excel 1.3 (http://dev.mysql.com/doc/mysql-for-excel/en/mysql-for-excel-what-is-new-1-3.html).

Functionality Added or Changed

  • A new Append Data advanced option was added, titled Confirm column mapping overwriting. When enabled, dragging and dropping source columns over target columns that were already mapped (in other words, they already contained a mapped source column) now triggers a confirmation dialog asking if the overwrite should be executed. This option is disabled by default as data overwrite is a common operation.
  • Added a new advanced option called Show column data types above column names. When checked, the Append Data dialog grid will show data type information for columns on source and target grids. This is especially helpful when manually mapping columns.
  • Added support for the JSON data type that was added in MySQL Server 5.7. The JSON data type is now selectable from the Export Data dialog, if the advanced option to show all data types is enabled. All data operations (Import, Export, Append and Edit) now function with the JSON data type.

Bugs Fixed

  • Attempting to save data to a column where the data can not be written (incompatible data type) now generates an error.
  • Changed the way data type related warnings are linked to grid columns in the Append Data dialog. Now the warnings are linked to the target (lower) grid view columns, because a single source column can be mapped to multiple target columns, and the warnings are about source data not being suitable for the target column’s data type.
  • When scrolling the target MySQL table grid horizontally, the upper column headers that contained names of the mapped source columns were not rendering text properly. The text moved while scrolling, and the column separators disappeared when scrolling to the right.
  • Change the data type detection logic for a column’s data that was failing when only the first row of data contained data, when the rest of the rows were empty.
  • The Append Data dialog was incorrectly mapping columns when only a single row of Excel data was selected to append. Also, if a single row of Excel data is selected with First Row Contains Column Names enabled, a warning is now displayed stating that no rows are available to complete the append operation.
  • Connection information created after the last save was cleared from memory when an Excel Workbook was closed, thus causing the connection information to not write to disk. Now the connection cleanup happens after a Workbook is saved, thereby saving the new connection information.
  • Stopped using hidden defined names to store formulas that transform date values into a date format used by MySQL. These defined names were being detected by Excel as macros or user functions that could not be saved in macro-free workbooks, thus generating bogus warnings every time a Workbook was saved when the Excel add-in was active.
  • Updated the data connection library to Connector/NET v6.9.8, which fixes the problem of accessing a schema that contained Unicode (non-ASCII) characters in its name. These databases now successfully open.
  • Deleted stored mappings would remain in the stored mapping method list.
  • Enhanced the custom grid view control used in the Append Data dialog to automatically adjust the width of the grid columns. This adjustment considers the grid’s cell contents, the base column header text, and also the contents of the additional header rows. Before, the target column width was too short.

 

Quick links:

Enjoy and thanks for the support!