mysql
mysql copied to clipboard
boostorg
MySQL C++ client based on Boost.Asio
The current interface for `resultset::async_read_some` and `resultset::async_read_all` doesn't allow to reuse memory or custom allocators. This has been flagged during the review as a possible performance issue. Proposed solutions: a)...
Provide a high-level explanation on the protocol in the docs, link back to the protocol, and explain the protocol evolution expectations.
Remove test cases in parametrized tests that don't add enough value, to reduce testing runtime.
Specify username and password (MySQL) for these containers.
All examples use text queries, which can be a security risk (SQL injection). Switch the focus to using prepared statements, instead.
Remove the line stating that the behavior of relational operators may change.
The bulleted list here is not formatted correctly: https://anarthal.github.io/mysql/mysql/ref/boost__mysql__row.html It should use `@li` for each list item, like this: https://github.com/boostorg/beast/blob/a593738e983514a14e1a8f9994b9a08cf809ca40/include/boost/beast/websocket/stream.hpp#L109
[This section](https://anarthal.github.io/mysql/mysql/values.html) is missing a paragraph on how to handle NULL values effectively. Provide an example showing something like: ``` value v = /* get the value */ if (v.is_null())...
Allow executing a one-off query with parameters without requiring the user to compose the query by string concatenation. Ideas: * Provide something similar to [mysql_real_escape_string](https://dev.mysql.com/doc/c-api/8.0/en/mysql-real-escape-string.html). * Create, execute and close...