Library / SDK
rbock/sqlpp11 avatar
rbock/sqlpp11

sqlpp11 asks you to migrate to sqlpp23, and its install instructions point at a releases page with no releases

A type safe SQL template library for C++

2,625 stars360 forksC++BSD-2-Clause

At a glance

What is it?
rbock/sqlpp11 is a template library that represents SQL queries as C++ types, with five bundled database connectors and compile time checks for syntax, type and name errors. The page carries a dated notice sending new development to a successor named after C++23, the compiler matrix lists Ubuntu 12.04 and Xcode 7, and the status table tracks two branches that are not the one you clone.
Who is it for?
Adopt sqlpp11 for new work only if you have a reason not to start on the successor, because the project's own notice says new development happens elsewhere and this line will be kept compiling rather than extended. Two things to check before you commit.
Can I use it commercially?
Yes. BSD-2-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • rbock/sqlpp112,625 ★ · +3
Star history
Repository2026-10-042026-11-15
rbock/sqlpp112.6k2.6k

3 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The build section sends you to a releases page with nothing on it

The build instructions open by telling you to download and unpack the latest release from the repository's releases page, or to clone the repository instead. The repository has no releases. Every published entry in its release list is absent, so the first half of that sentence leads to an empty page and only the clone half works. The commands themselves are the modern two step form, one to configure into a build directory and one to build and install:

bash
cmake -B build
cmake --build build --target install

The page does warn that the install step writes system wide and may therefore need administrator rights, and it notes that you might not need to install anything at all depending on how you consume the library, which is the header-only path. So the instructions are careful about everything except the one link that does not resolve to anything.

A dated notice redirects new work to sqlpp23

The first block on the page is not an introduction, it is a notice with a date attached: 2025-06-29. It asks readers to consider migrating to a different repository named after the newer C++ standard, and states that this library will be maintained for the foreseeable future while new development happens in the successor only. Three things follow from a notice written that way. The project is in maintenance by its own declaration, so a new feature request here is a request to the other repository. The successor skips a version number rather than continuing one, which tells you it is a rewrite rather than a release line. And the notice is frozen: the date in the block has not been touched since it was written, and the sentence announcing the succession still reads as news rather than as history.

The compiler matrix lists Ubuntu 12.04, Xcode 7 and MSVC 2015

The requirements section is precise about wording and then lists toolchains from another decade. It says the library makes heavy use of C++11 and needs a recent compiler and standard library, then gives the compilers known to compile the test programs: clang from 3.4 and g++ from 4.8 on a particular Ubuntu release, g++ on 64 bit Cygwin, g++ 4.9 on Debian unstable, Xcode 7 on macOS, and MSVC 2015 Update 1 on Windows Server 2012. Read the verb rather than the version numbers. This is a statement about what has been observed to build the tests, not a support policy, and a 2026 reader with a current toolchain learns from it that the matrix has not been refreshed. For a header heavy template library that is also useful information: the era of the listed compilers is roughly the era of the library's design.

The status table tracks two branches you do not get by default

A table near the bottom of the page lists two branches, one named master and one named develop, and for each of them gives three badges: continuous integration for the clang and gcc builds, a second badge for MSVC, and a coverage badge. Both services in those badge URLs are long retired as hosted continuous integration providers, and both are still configured in the repository as files. The default branch, meanwhile, is neither of the two in the table: it is a third name. So a reader who clones the repository gets a branch that the status table does not describe, and a reader who reads the status table learns which two branches the badges were once measuring. The table is a snapshot of a working arrangement that has since been reorganised, and it is still the only place the page reports on testing.

Date and time types arrive from another library at configure time

Two of the data types the library models, date and date time, are not implemented here. They come from a well known standalone date library, which the page links and names, and which is required rather than optional. How you get it depends on one switch. By default the build uses CMake's fetch capability to pull the library automatically as part of configuring, which means configuring the project is a network operation whether you intended one or not. If you would rather use a copy you already have installed, there is an option that switches to locating it with the package finder instead. This is a reasonable design and a real dependency decision for a library used in builds that are supposed to be hermetic, and it is worth knowing before a build fails in an environment with no network access.

The second example stops in the middle of a statement

The examples section opens with a table definition of three columns, an integer, a short string and a boolean, then assumes a connection object and shows two loops. The first one selects named columns, filters with a conjunction and a pattern match, and iterates rows, checking a field for null before converting it, with the two conversions written as plain assignments because string-like fields and boolean fields convert implicitly. That part is the clearest demonstration of the design on the page: a result row is a struct with named, typed members, and the null check is a method on the member. The second example starts by selecting all columns of a table and then ends, mid statement, with an open parenthesis and no closing brace. A reader copying from the page has the first example to work from and none of the second.

Database differences are pushed into the connector, on purpose

The core of the library is vendor neutral, and the page is explicit about where vendor specifics are supposed to live: in connector libraries. That division has three consequences worth stating. A connector can tell a developer at compile time that a feature is missing or non standard on that database, so portability problems surface as build errors rather than as runtime surprises. A connector can also interpret an expression where it needs to, and the example given is string concatenation, where one database might use the concatenation operator and another a function call, and the developer writes the same statement either way. And a third party can add support without touching the core, which is why an ODBC connector lives in someone else's repository and is marked experimental. Five connectors ship here: MySQL, MariaDB, SQLite3, SQLCipher and PostgreSQL.

The public record for the library stops in 2015

The page collects conference talks about the library, and the dates run from February 2014 to September 2015 across four conference series, with the last entry being a talk about pruning error messages from template code, illustrated with examples from this library. That talk is the most telling item in the list. A template metaprogramming library's usability problem is that its error messages are enormous, and the project answered that with a talk rather than with a design change, which tells you what the hard part has always been. Nothing in the list is newer than 2015. The rest of the root is consistent with a library that consolidated rather than grew: a formatting configuration, two continuous integration files, a coverage upload script and a hook script committed as files, a site configuration for the hosted documentation, and a wishlist file kept in the open.

Editorial conclusion

Adopt sqlpp11 for new work only if you have a reason not to start on the successor, because the project's own notice says new development happens elsewhere and this line will be kept compiling rather than extended. Two things to check before you commit. Read the compiler matrix, because the page lists the toolchains known to build its tests and they are a decade old, which tells you what is tested rather than what works. And read the build options, because only the core library is installed by default and the connectors are opt in one at a time, each with its own dependency check you can turn off. If you are picking between this and its successor, the migration notice is dated and specific, which makes the decision easier than the surrounding prose suggests.

Frequently asked questions

What is sqlpp11?

A type safe embedded domain specific language for SQL queries and results in C++. Tables and columns are represented as types, queries are checked at compile time for syntax, type and name errors, and results are iterated as query specific structs with named members.

Is sqlpp11 still being developed?

The page carries a notice dated 2025-06-29 asking users to consider migrating to sqlpp23, saying sqlpp11 will be maintained for the foreseeable future while new development happens in the successor only. The last push to the repository is dated 2026-04-24.

Which databases does sqlpp11 support?

Connectors for MySQL, MariaDB, SQLite3, SQLCipher and PostgreSQL are included in the repository. An ODBC connector lives in another repository and is marked experimental, and the core itself is vendor neutral with database traits handled by the connector.

How do I build and install sqlpp11?

With two commands, one to configure into a build directory and one to build and install, which installs system wide and may need administrator rights. Only the core library is installed by default, with one option per connector and a switch to skip the dependency check.

What compilers does sqlpp11 support?

The page lists the compilers known to compile its test programs: clang 3.4 and g++ 4.8 on an old Ubuntu release, g++ on 64 bit Cygwin, g++ 4.9 on Debian unstable, Xcode 7 on macOS, and MSVC 2015 Update 1 on Windows Server 2012.

What date library does sqlpp11 need?

Howard Hinnant's date library, required for the date and date time data types. By default the build fetches it automatically while configuring, and one option switches to using an already installed copy located with the package finder instead.

Official sources

  1. Issues
  2. License: BSD-2-Clause
  3. rbock/sqlpp11 on GitHub
  4. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/rbock-sqlpp11.svg)](https://hysenlabs.com/projects/rbock-sqlpp11)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/rbock-sqlpp11.svg)](https://hysenlabs.com/projects/rbock-sqlpp11)

Was this useful?