This fixes bugs since the first GA release 1.0.5 and introduces new features.
API incompatible change:
is no longer a
struct by a typedef that uses
boost::variant. Code such as:
sql::ConnectPropertyVal tmp; tmp.str.val=passwd.c_str(); tmp.str.len=passwd.length(); connection_properties["password"] = tmp;
Should be changed to:
connection_properties["password"] = sql::ConnectPropertyVal(passwd);
std::auto_ptr have been changed
boost::scoped_ptr. Scoped array instances
now use boost::scoped_array. Further,
boost::weak_ptr are now used for guarding
access around result sets.
Connection map property
changed to be of type
get_driver_instance() is now only available
in dynamic library builds - static builds do not have this
symbol. This was done to accommodate loading the DLL with
you do not use CMake for building the source
code you will need to define
mysqlcppconn_EXPORTS if you are loading
dynamically and want to use the
get_driver_instance() entry point.
Connection::getClientOption(const sql::SQLString &
optionName, void * optionValue) now accepts the
characterSetResults. In the previous version
metadataUseInfoSchema was permitted. The
same options are available for
CPPFLAGS are now checked from the environment
for every binary generated.
Certain header files were incorrectly present in the source distribution. The fix excludes dynamically generated and platform specific header files from source packages generated using CPack. (Bug #45846)
CMake generated an error if configuring an out of source build, that is, when CMake was not called from the source root directory. (Bug #45843)
Using Prepared Statements caused corruption of the heap. (Bug #45048)
Missing includes when using GCC 4.4. Note that GCC 4.4 is not yet in use for any official Connector/C++ builds. (Bug #44931)
A bug was fixed in Prepared Statements. The bug occurred when a stored procedure was prepared without any parameters. This led to an exception. (Bug #44931)
Fixed a Prepared Statements performance issue. Reading large result sets was slow.
Fixed bug in
ResultSetMetaData for statements
and prepared statements,
getPrecision returned incorrect results.