nanodbc - C++ wrapper for ODBC API¶
nanodbc is a small library that makes ODBC API programming easy and fun again.
Documentation for the latest version v2.13.0.
Here’s a before and after look at straight ODBC C API code and its equivalent nanodbc code.
The native C API for working with ODBC is exorbitantly verbose, ridiculously complicated, and fantastically brittle. nanodbc addresses these frustrations! The goal for nanodbc is to make developers happy.
The nanodbc philosophy states: common database programming tasks should be easy, requiring concise and simple code.
To accommodate users who can not use the latest and greatest, semantic versioning and release notes will clarify required C++ features and/or standards for particular versions.
Originally nanodbc began as a simple fork of TinyODBC with additional features. Eventually it grew to the point where it made sense to break with many of the basic underlaying design decisions of TinyODBC and completely refactor much of the codebase. Other projects that have had influence on nanodbc include SimpleDB, pyodbc, Database Template Library, and GSODBC.
Why should you use nanodbc?
Small! Same as TinyODBC, nanodbc is small. A header and an implementation file.
Simple! There are only a handful of significant classes to learn.
Portable! nanodbc uses only standard C++ headers in addition to the ODBC API headers.
Robust! Where it makes sense, error handling is done with exceptions instead of return codes.
Features! nanodbc supports ODBC 3, SQLDriverConnect(), Transactions, Bound Parameters, Bulk Operations, and much more.
Documented! I have tried to provide very clean and useful documentation with example usage.
Active! I am currently actively using and developing nanodbc so I hope to add more and more features all the time.
All complex objects in nanodbc follow the pimpl (Pointer to IMPLementation) idiom to provide separation between interface and implementation, value semantics, and a clean nanodbc.h header file that includes nothing but standard C++ headers.
nanodbc wraps ODBC code, providing a simpler way to do the same thing. We try to be as featureful as possible, but I can’t guarantee you’ll never have to write supporting ODBC code. Personally, I have never had to do so.
Major features beyond what’s already supported by ODBC are not within the scope of nanodbc. This is where the nano part of nanodbc becomes relevant: This library is as minimal as possible. That means no dependencies beyond standard C++ and typical ODBC headers. No features unsupported by existing ODBC API calls.