El mié., 4 mar. 2020 10:18, Andrey Semashev via Boost
On Wed, Mar 4, 2020 at 12:32 PM Joseph Van Riper via Boost
wrote: On Tue, Mar 3, 2020 at 8:50 PM Ruben Perez via Boost <
boost@lists.boost.org>
wrote:
I have been writing an ASIO-based client for MySQL, trying to mimic
what
Beast is to HTTP. It currently supports SQL queries and prepared statements. It can be viewed here:
https://github.com/anarthal/mysql-asio
Do you guys think this has the potential to be useful or become part of Boost long term? Any feedback is very welcome.
Why just MySQL?
I would take more interest in a library capable of supporting many database engines. Or, if not such a variety, at least target ODBC, as you can reach more engines through ODBC drivers.
While I understand many people like MySQL, some use cases call for other engines (like SQLite3, providing a lightweight, simple database file without all the overhead of MySQL). For a boost library, I would hope it would not limit the developer to a single engine.
+1
I don't see the point of having a Boost wrapper for just one specific backend. People who want that could just use MySQL C or C++ API directly.
Just to clarify, this is *not* a wrapper around the MySQL C API, it is an implementation of the MySQL protocol based in ASIO. I see this as a building block, that can be used by any other bigger, more abstract library providing multiple backends. This library takes the approach of doing a single thing well. It provides no abstraction over MySQL specifics. But it can be seen as a step towards something bigger. The other value I see in this is that it is Asio-based. So it would contribute towards the creation of an Asio-based ecosystem. The aim is to integrate well with any project that uses Asio (e.g. using Beast), which I don't think the MySQL C++ API gives you.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost