MySQL Connector/C++ 1.1.5 has been released
karen langford <[email protected]>
| Newsgroups | gmane.comp.db.mysql.general,gmane.comp.db.mysql.packagers |
|---|---|
| Organization | Oracle Corporation |
| Message-ID | <[email protected]> |
Dear MySQL Users,
A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.5 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 has used it successfully for 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.5 (2014-11-26)
Functionality Added or Changed
* It was not possible to delete multiple connection
attributes using the OPT_CONNECT_ATTR_DELETE option. This
can now be done using the std::list< sql::SQLString >
type. (Bug #19939417)
* MySQL_Prepared_Statement::getMoreResults() functionality
has been implemented, so multiple result sets now can be
fetched using a prepared statement. (Bug #19147677)
* The following connection options have been implemented:
MYSQL_DEFAULT_AUTH, MYSQL_OPT_CONNECT_ATTR_DELETE,
MYSQL_OPT_CONNECT_ATTR_RESET, MYSQL_OPT_LOCAL_INFILE,
MYSQL_PLUGIN_DIR, MYSQL_READ_DEFAULT_FILE,
MYSQL_READ_DEFAULT_GROUP, MYSQL_SET_CHARSET_DIR, and
max_statement_timeout for session-based query timeout.
(Bug #73665, Bug #19479950)
* These functions were added: Connection::isValid() checks
whether the connection is alive, and
Connection::reconnect() reconnects if the connection has
gone down. (Bug #65640, Bug #14207722)
* The Boost dependency was removed from the Connector/C++
API headers. These headers were using the boost::variant
type, making it impossible to use Connector/C++ binaries
without having Boost installed.
Bugs Fixed
* For installation from MSI packages, variant.h and
version_info.h were missing from the include/cppconn
folder. (Bug #19973637)
* For several valid client options, getClientOption() did
not return a value. (Bug #19940314)
* A memory leak occurred when adding the
OPT_CONNECT_ATTR_ADD parameter to the options list.
(Bug #19938970)
* getClientOption() raised an assertion if the specified
option was not set at connect time. (Bug #19938922)
* Several metadata flaws were corrected:
+ getTables() did not return a correct result when
TableType=VIEW and metadataUseInfoSchema=false.
+ getColumns() did not return column inforomation when
metadataUseInfoSchema=TRUE.
+ getColumnName() returned the display name instead of
the actual column name.
+ getProcedures() returned a syntax error when
metadataUseInfoSchema=false.
(Bug #19505348, Bug #19147897, Bug #19244736, Bug
#19505421)
* The LOCALHOST global variable was referenced at two
places in C/C++ code, which could result in a double-free
corruption error. (Bug #74616, Bug #19910311)
* driver/version_info.h (containing version macros) was not
included in the installed header files.
(Bug #73795, Bug #19553971)
* Several CMake issues were corrected:
+ CMake could misconfigure the link flags.
+ CMake did not pick up the libmysqlclient path from
the MYSQL_LIB_DIR option.
+ For test suite compilation, CMake did not pick up
libmysqlclient from the user-specified path, even if
MYSQL_LIB_DIR and DYNLOAD_MYSQL_LIB were given.
(Bug #73427, Bug #19315635, Bug #19370844, Bug #19940663)
* Connector/C++ issued a ping command every time isClosed()
was called in a Connection, rather than just checking
whether close() had been called earlier or when a fatal
error occurred in an earlier operation.
(Bug #69785, Bug #17186530)
* With the result set type set to TYPE_FORWARD_ONLY,
Statement::executeQuery() returns almost immediately, but
MySQL_ResultSet::next() and
MySQL_Prepared_ResultSet::next() returned false if the
connection was lost rather than throwing an exception,
making it impossible to distinguish loss of connection
from normal end of the result set.
MySQL_ResultSet::next() and
MySQL_Prepared_ResultSet::next() now throw an exception
when the connection is lost. (Bug #69031, Bug #18886278)
* Connection objects shared internal state with Statement
objects they spawned, preventing a connection close
unless the Statement objects were destroyed first. A
connection to the server now is closed by calling
Connection::close() and invoking the Connection object
destructor, without explicitly destroying the statement
object.
On Behalf of the MySQL/ORACLE RE Team,
Kent Boortz
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql