sqlpp11

A type safe embedded domain specific language for SQL queries and results in C++

Extensive documentation is found in the wiki, https://github.com/rbock/sqlpp11/wiki

Past talks/workshops at

• CppCast: http://cppcast.com
• 2015-05-07: http://cppcast.com/2015/05/roland-bock/
• CppCon (Bellevue, Washington, USA): http://cppcon.org
• 2014-09-08: http://sched.co/1qhngYK (Workshop Part 1)
• 2014-09-11: http://sched.co/1r4lue3 (Talk)
• 2014-09-12: http://sched.co/Wi8aWM (Workshop Part 2)
• MeetingC++ (Berlin, Germany): http://meetingcpp.com/index.php/mcpp2014.html
• 2014-12-05:http://meetingcpp.com/index.php/tv14/items/4.html

You can contact me

• by posting issues at https://github.com/rbock/sqlpp11/issues
• or via email at rbock at eudoxos dot de

Motivation:

SQL and C++ are both strongly typed languages. Still, most C/C++ interfaces to SQL are based on constructing queries as strings and on interpreting arrays or maps of strings as results.

sqlpp11 is a templated library representing an embedded domain specific language (EDSL) that allows you to

• define types representing tables and columns,
• construct type safe queries checked at compile time for syntax errors, type errors, name errors and even some semantic errors,
• interpret results by iterating over query-specific structs with appropriately named and typed members.

This results in several benefits, e.g.

• the library user operates comfortably on structs and functions,
• the compiler reports many kinds of errors long before the code enters unit testing or production,
• the library hides the gory details of string construction for queries and interpreting results returned by select calls.

The library supports both static and dynamic queries. The former offers greater benefit in terms of type and consistency checking. The latter makes it easier to construct queries on the flight.

sqlpp11 is vendor-neutral. Specific traits of databases (e.g. unsupported or non-standard features) are are handled by connector libraries. Connector libraries can inform the developer of missing features at compile time. They also interpret expressions specifically where needed. For example, the connector could use the operator|| or the concat method for string concatenation without the developer being required to change the statement.

Your help is needed:

The library is already used in production but it is certainly not complete yet. Feature requests, bug reports, contributions to code or documentation are most welcome.

Examples:

For the examples, lets assume you have a table class representing something like

CREATE TABLE foo (
    id bigint,
    name varchar(50),
    hasFun bool
);

And we assume to have a database connection object:

TabFoo foo;
Db db(/* some arguments*/);

// selecting zero or more results, iterating over the results
for (const auto& row : db(select(foo.name, foo.hasFun).from(foo).where(foo.id > 17 and foo.name.like("%bar%"))))
{
    if (row.name.is_null())
        std::cerr << "name is null, will convert to empty string" << std::endl;
    std::string name = row.name;   // string-like fields are implicitly convertible to string
    bool hasFun = row.hasFun;          // bool fields are implicitly convertible to bool
}

// selecting ALL columns of a table
for (const auto& row : db(select(all_of(foo)).from(foo).where(foo.hasFun or foo.name == "joker")))
{
    int64_t id = row.id; // numeric fields are implicitly convertible to numeric c++ types
}

// selecting zero or one row, showing off with an alias:
SQLPP_ALIAS_PROVIDER(cheese);
if (const auto& row = db(select(foo.name.as(cheese)).from(foo).where(foo.id == 17)))
{
    std::cerr << "found: " << row.cheese << std::endl;
}

// selecting a single row with a single result:
return db(select(count(foo.id)).from(foo).where(true)).front().count;

Of course there are joins and subqueries, more functions, order_by, group_by etc.
These will be documented soon.

// A sample insert
db(insert_into(foo).set(foo.id = 17, foo.name = "bar", foo.hasFun = true));

// A sample update
db(update(foo).set(foo.hasFun = not foo.hasFun).where(foo.name != "nobody"));

// A sample delete
db(remove_from(foo).where(not foo.hasFun));

Requirements:

Compiler: sqlpp11 makes heavy use of C++11 and requires a recent compiler and STL. The following compilers are known to compile the test programs:

• clang-3.2 on Ubuntu-12.4
• clang-3.4 on Ubuntu-12.4
• g++-4.8 on Ubuntu-12.4
• g++-4.8 on cygwin 64bit
• g++-4.9 on Debian Unstable

Database Connector: sqlpp11 requires a certain api in order to connect with the database, see database/api.h.

• MySQL: https://github.com/rbock/sqlpp11-connector-mysql
• Sqlite3: https://github.com/rbock/sqlpp11-connector-sqlite3
• PostgreSQL: https://github.com/matthijs/sqlpp11-connector-postgresql

To demonstrate that sqlpp11 can work with other backends as well, here is an experimental backend for structs in standard containers:

• STL Container: https://github.com/rbock/sqlpp11-connector-stl