mysql
mysql copied to clipboard
boostorg
MySQL C++ client based on Boost.Asio
https://anarthal.github.io/mysql/mysql/resultsets.html#mysql.resultsets.complete states a protocol limitation, but there is a library limitation, too (we could do a better job and implement a degree of pipelining). #75 addresses implementing pipelining. Until this...
Implement client-side pipelining of requests. When executing a text query or a prepared statement, the following packet exchange occurs: ``` client server ----- query request --->
Provide a helper functions to make these cases easier: * A query returning a single value, e.g. a `SELECT COUNT(*)` statement. * A query returning an empty resultset, e.g. `INSERT`...
Support ``` statement.execute("hello", "world", 42); statement.async_execute("hello", "world", 42, use_future); ```
* Includes in the docs * Link to the source code in the docs * Rename employees => hello_resultset
Allow calling `connection::connect` with an argument satisfying the `EndpointSequence` concept, as returned by `basic_resolver::resolve`.
Add something in the main page and README stating the difference between a protocol library like this and a framework/ORM like sqlpp11.
Provide helper functions `connection::start_transaction`, `connection::commit` and `connection::rollback` (and their async counterparts).
https://dev.mysql.com/doc/refman/8.0/en/load-data.html When issuing such a query, the server answers with a GET_MORE_CLIENT_DATA (type 0xfb) as seen in [this diagram](https://dev.mysql.com/doc/internals/en/com-query-response.html#packet-COM_QUERY_Response). Add support for this.
Add a warning to the documentation of `connection::query` about the risks on SQL injection attacks when not using the function properly.