In order to let more people experience type safety and other compile time constraints when programming SQL in C++, more connectors for sqlpp11 are required. Currently there are connectors for MySQL/MariaDb, Postgresql and Sqlite3, as well as an experimental binding to std::vector.
I would like to use the opportunity of having so many capable people in one place to try to add a few more connector libraries. These libraries would not be finished by the end of the day, but there are pretty good chances to get the first few queries processed.
"The compile time query checks are brilliant." dirkvdb
sqlpp11 is an EDSL for SQL in C++, allowing you to write SQL queries in name- and type-safe manner. You can learn a lot about how it works and how you benefit from it in my talk on Thursday.
sqlpp11 is vendor neutral. In order to work with a database, it requires a connector library. Such libraries are available for MySQL/MariaDb, PostgreSQL, Sqlite3 and (experimental) std::vector.
I want to use the opportunity of having so many highly capable developers in one place: Lets write a few more connector libraries. These could be for SQL databases, like Microsoft SQL, Oracle, Firebird, MemSQL, DB2 etc. If you're feeling more adventurous, we could at least start writing connectors to other databases, e.g. incoming JSON streams, or we could improve on the connector to C++ standard containers.
I'll start with a short introduction about what a connector looks like and how it is typically structured. After that we start coding (in teams, maybe). I will provide a skeleton so that you don't have to worry less about structure and boiler plate. I am sure that we will be successfully processing the first queries with new connectors by the end of the session.
Anyone can participate. It would be helpful if you
