Dear MySQL users,

MySQL Connector/C++ 2.0.3 is the next development milestone of the MySQL
Connector/C++ 2.0 series, and the first public release. Apart from
covering more X DevAPI features, it adds a new, plain C API, called
XAPI, that offers functionality similar to X DevAPI to applications
written in plain C. Thus, not only can MySQL Connector/C++ be used to
write C++ applications, as before. Now, using the XAPI, MySQL
Connector/C++ can be used to write plain C applications to access MySQL
Database implementing a document store as well as execute traditional
plain SQL statements. For more information about XAPI, refer to the
documentation at
http://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html.

To learn more about how to write applications using the X DevAPI, see X
DevAPI User Guide (http://dev.mysql.com/doc/x-devapi-userguide/en/). For
more information about how to use Connector/C++ 2.0 and how the X DevAPI
is implemented in it, see http://dev.mysql.com/doc/dev/connector-cpp/.

Note

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 Using MySQL as a Document
Store (http://dev.mysql.com/doc/refman/5.7/en/document-store.html).

To download MySQL Connector/C++ 2.0.3 m3, see the "Development Releases"
tab at http://dev.mysql.com/downloads/connector/cpp/

X DevAPI Notes

     * New X DevAPI features added in this MySQL Connector/C++
       release:

          + Methods for starting and controlling transactions

          + Using an X DevAPI URI or connection string to
            specify new session parameters

          + Capability of binding a session to the default shard
            and execute SQL statements there (using
            XSession.bindToDefaultShard())

          + Methods for counting elements in a table or
            collection

          + Access to multiple result sets if present in a query
            result

          + Methods to count items in a result set and fetch a
            complete result set at once (using fetchAll()),
            instead of accessing items one by one (using
            fetchOne())

          + Access to warnings reported when processing a
            statement (getWarnings())

          + Access to information about affected rows, generated
            auto-increment values, and identifiers of documents
            added to a collection


On Behalf of the MySQL/ORACLE RE Team


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql

Reply via email to