MySQL Forums
Forum List  »  Announcements

MySQL Connector/C++ 1.1.4 has been released
Posted by: Sowmya Dass
Date: July 31, 2014 02:41PM


Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.4 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/cpp/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. 


The MySQL driver for C++ offers an easy to use API derived from JDBC
4.0. MySQL Workbench is using it successfully since years.

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!

The MySQL build team at Oracle

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

Changes in MySQL Connector/C++ 1.1.4 (2014-07-31)

   Functionality Added or Changed

     * Connector/C++ now supports the following connection options:
       sslVerify (boolean), sslCRL (string), and sslCRLPath (string).
       These correspond to the MYSQL_OPT_SSL_VERIFY_SERVER_CERT,
       MYSQL_OPT_SSL_CRL, and MYSQL_OPT_SSL_CRLPATH options for the
       mysql_options() C API function. (Bug #18461451)

     * Connector/C++ has new functions to provide schema, table, and
       column character set and collation metadata for result sets:

          + ResultSet * DatabaseMetaData::getSchemaCollation(const
            sql::SQLString& catalog, const sql::SQLString&
            schemaPattern)

          + ResultSet * DatabaseMetaData::getSchemaCharset(const
            sql::SQLString& catalog, const sql::SQLString&
            schemaPattern)

          + ResultSet * DatabaseMetaData::getTableCollation(const
            sql::SQLString& catalog, const sql::SQLString&
            schemaPattern, const sql::SQLString& tableNamePattern)

          + ResultSet * DatabaseMetaData::getTableCharset(const
            sql::SQLString& catalog, const sql::SQLString&
            schemaPattern, const sql::SQLString& tableNamePattern)

          + SQLString ResultSetMetaData::getColumnCollation(unsigned
            int columnIndex)

          + SQLString ResultSetMetaData::getColumnCharset(unsigned
            int columnIndex)
       (Bug #72698, Bug #18803345)

     * Connector/C++ now supports the MYSQL_OPT_CONNECT_ATTR_ADD
       option, which accepts an std::map argument. This option
       corresponds to the MYSQL_OPT_CONNECT_ATTR_ADD option for
       mysql_options4(). (Bug #72697, Bug #18803313)

     * Connector/C++ now supports a useLegacyAuth connection option,
       which corresponds to the MYSQL_SECURE_AUTH option for
       mysql_options(). (Bug #69492, Bug #16970753)

     * Connector/C++ is now compiled and linked with Connector/C
       6.1.5 rather than with libmysql.

   Bugs Fixed

     * MySQL_ResultSetMetaData::getColumnTypeName() returned UNKNOWN
       for LONG_BLOB fields. (Bug #72700, Bug #18803414)

     * Connector/C++ version-information methods have been revised to
       return the correct values. (Bug #66975, Bug #14680878)

     * Definitions for character sets and collations were added
       (utf8mb4 in particular). (Bug #71606, Bug #18193771)

Documentation
--------------
Online:http://dev.mysql.com/doc/connector-cpp/en/index.html

Reporting Bugs
---------------
We welcome and appreciate your feedback and bug reports:
http://bugs.mysql.com/       

On Behalf of the MySQL RE team at Oracle,
Sowmya Dass



Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Connector/C++ 1.1.4 has been released
2502
July 31, 2014 02:41PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.