lmdb++: a C++11 wrapper for LMDB

.. image:: https://api.travis-ci.org/bendiken/lmdbxx.svg?branch=master :target: https://travis-ci.org/bendiken/lmdbxx :alt: Travis CI build status

.. image:: https://scan.coverity.com/projects/4900/badge.svg :target: https://scan.coverity.com/projects/4900 :alt: Coverity Scan build status

This is a comprehensive C++ wrapper for the LMDB_ embedded database library, offering both an error-checked procedural interface and an object-oriented resource interface with RAII_ semantics.

.. LMDB: http://symas.com/mdb/ .. _RAII: http://en.wikipedia.org/wiki/ResourceAcquisitionIsInitialization

Example

Here follows a simple motivating example_ demonstrating basic use of the object-oriented resource interface::

#include #include #include

int main() { /* Create and open the LMDB environment: / auto env = lmdb::env::create(); env.set_mapsize(1UL * 1024UL * 1024UL * 1024UL); / 1 GiB */ env.open("./example.mdb", 0, 0664);

 /* Insert some key/value pairs in a write transaction: */
 auto wtxn = lmdb::txn::begin(env);
 auto dbi = lmdb::dbi::open(wtxn, nullptr);
 dbi.put(wtxn, "username", "jhacker");
 dbi.put(wtxn, "email", "[email protected]");
 dbi.put(wtxn, "fullname", "J. Random Hacker");
 wtxn.commit();

 /* Fetch key/value pairs in a read-only transaction: */
 auto rtxn = lmdb::txn::begin(env, nullptr, MDB_RDONLY);
 auto cursor = lmdb::cursor::open(rtxn, dbi);
 std::string key, value;
 while (cursor.get(key, value, MDB_NEXT)) {
   std::printf("key: '%s', value: '%s'\n", key.c_str(), value.c_str());
 }
 cursor.close();
 rtxn.abort();
 /* The enviroment is closed automatically. */
 return EXIT_SUCCESS;

}

Should any operation in the above fail, an

lmdb::error

.. note::

In order to run this example, you must first manually create the

./example.mdb

.. _example: https://github.com/bendiken/lmdbxx/blob/master/example.cc#L1

Features

• Designed to be entirely self-contained as a single
  header file that can be dropped into a project.
• Implements a straightforward mapping from C to C++, with consistent naming.
• Provides both a procedural interface and an object-oriented RAII interface.
• Simplifies error handling by translating error codes into C++ exceptions.
• Carefully differentiates logic errors, runtime errors, and fatal errors.
• Exception strings include the name of the LMDB function that failed.
• Plays nice with others: all symbols are placed into the

  lmdb

  namespace.
• 100% free and unencumbered

  public domain 

  _ software, usable in any context and for any purpose.

Requirements

The

In addition, for your application to build and run, the underlying

liblmdb

liblmdb-dev

.. _Clang: http://clang.llvm.org/ .. _GCC: http://gcc.gnu.org/

Overview

This wrapper offers both an error-checked procedural interface and an object-oriented resource interface with RAII semantics. The former will be useful for easily retrofitting existing projects that currently use the raw C interface, but we recommend the latter for all new projects due to the exception safety afforded by RAII semantics.

Resource Interface

The high-level resource interface wraps LMDB handles in a loving RAII embrace. This way, you can ensure e.g. that a transaction will get automatically aborted when exiting a lexical scope, regardless of whether the escape happened normally or by throwing an exception.

============================ =================================================== C handle C++ wrapper class ============================ ===================================================

MDB_env*

lmdb::env

MDB_txn*

lmdb::txn

MDB_dbi

lmdb::dbi

MDB_cursor*

lmdb::cursor

MDB_val

lmdb::val

The methods available on these C++ classes are named consistently with the procedural interface, below, with the obvious difference of omitting the handle type prefix which is already implied by the class in question.

Procedural Interface

The low-level procedural interface wraps LMDB functions with error-checking code that will throw an instance of a corresponding C++ exception class in case of failure. This interface doesn't offer any convenience overloads as does the resource interface; the parameter types are exactly the same as for the raw C interface offered by LMDB itself. The return type is generally

void

This interface is implemented entirely using static inline functions, so there are no hidden extra costs to using these wrapper functions so long as you have a decent compiler capable of basic inlining optimization.

============================ =================================================== C function C++ wrapper function ============================ ===================================================

mdb_version()

mdb_strerror()

mdb_env_create()

lmdb::env_create()

mdb_env_open()

lmdb::env_open()

mdb_env_copy()

lmdb::env_copy()

mdb_env_copyfd()

lmdb::env_copy_fd()

mdb_env_copy2()

lmdb::env_copy()

mdb_env_copyfd2()

lmdb::env_copy_fd()

mdb_env_stat()

lmdb::env_stat()

mdb_env_info()

lmdb::env_info()

mdb_env_sync()

lmdb::env_sync()

mdb_env_close()

lmdb::env_close()

mdb_env_set_flags()

lmdb::env_set_flags()

mdb_env_get_flags()

lmdb::env_get_flags()

mdb_env_get_path()

lmdb::env_get_path()

mdb_env_get_fd()

lmdb::env_get_fd()

mdb_env_set_mapsize()

lmdb::env_set_mapsize()

mdb_env_set_maxreaders()

lmdb::env_set_max_readers()

mdb_env_get_maxreaders()

lmdb::env_get_max_readers()

mdb_env_set_maxdbs()

lmdb::env_set_max_dbs()

mdb_env_get_maxkeysize()

lmdb::env_get_max_keysize()

mdb_env_set_userctx()

lmdb::env_set_userctx()

mdb_env_get_userctx()

lmdb::env_get_userctx()

mdb_env_set_assert()

mdb_txn_begin()

lmdb::txn_begin()

mdb_txn_env()

lmdb::txn_env()

mdb_txn_id()

lmdb::txn_id()

mdb_txn_commit()

lmdb::txn_commit()

mdb_txn_abort()

lmdb::txn_abort()

mdb_txn_reset()

lmdb::txn_reset()

mdb_txn_renew()

lmdb::txn_renew()

mdb_dbi_open()

lmdb::dbi_open()

mdb_stat()

lmdb::dbi_stat()

mdb_dbi_flags()

lmdb::dbi_flags()

mdb_dbi_close()

lmdb::dbi_close()

mdb_drop()

lmdb::dbi_drop()

mdb_set_compare()

lmdb::dbi_set_compare()

mdb_set_dupsort()

lmdb::dbi_set_dupsort()

mdb_set_relfunc()

lmdb::dbi_set_relfunc()

mdb_set_relctx()

lmdb::dbi_set_relctx()

mdb_get()

lmdb::dbi_get()

mdb_put()

lmdb::dbi_put()

mdb_del()

lmdb::dbi_del()

mdb_cursor_open()

lmdb::cursor_open()

mdb_cursor_close()

lmdb::cursor_close()

mdb_cursor_renew()

lmdb::cursor_renew()

mdb_cursor_txn()

lmdb::cursor_txn()

mdb_cursor_dbi()

lmdb::cursor_dbi()

mdb_cursor_get()

lmdb::cursor_get()

mdb_cursor_put()

lmdb::cursor_put()

mdb_cursor_del()

lmdb::cursor_del()

mdb_cursor_count()

lmdb::cursor_count()

mdb_cmp()

mdb_dcmp()

mdb_reader_list()

mdb_reader_check()

.. rubric:: Footnotes

.. [1] Three-parameter signature available since LMDB 0.9.14 (2014/09/20).

.. [2] Only available since LMDB 0.9.11 (2014/01/15).

.. [3] Only available in LMDB HEAD, not yet in any 0.9.x release (as of 0.9.16). Define the

LMDBXX_TXN_ID

.. [4] Note the difference in naming. (See below.)

Caveats ^^^^^^^

• The C++ procedural interface is more strictly and consistently grouped by handle type than is the LMDB native interface. For instance,

  mdb_put()

  is wrapped as the C++ function

  lmdb::dbi_put()

  , not

  lmdb::put()

  . These differences--a handful in number--all concern operations on database handles.

• The C++ interface takes some care to be const-correct for input-only parameters, something the original C interface largely ignores. Hence occasional use of

  const_cast

  in the wrapper code base.

• lmdb::dbi_put()

  does not throw an exception if LMDB returns the

  MDB_KEYEXIST

  error code; it instead just returns

  false

  . This is intended to simplify common usage patterns.

• lmdb::dbi_get()

  ,

  lmdb::dbi_del()

  , and

  lmdb::cursor_get()

  do not throw an exception if LMDB returns the

  MDB_NOTFOUND

  error code; they instead just return

  false

  . This is intended to simplify common usage patterns.

• lmdb::env_get_max_keysize()

  returns an unsigned integer, instead of a signed integer as the underlying

  mdb_env_get_maxkeysize()

  function does. This conversion is done since the return value cannot in fact be negative.

Error Handling

This wrapper draws a careful distinction between three different classes of possible LMDB error conditions:

• Logic errors, represented by

  lmdb::logic_error

  . Errors of this class are thrown due to programming errors where the function interfaces are used in violation of documented preconditions. A common strategy for handling this class of error conditions is to abort the program with a core dump, facilitating introspection to locate and remedy the bug.
• Fatal errors, represented by

  lmdb::fatal_error

  . Errors of this class are thrown due to the exhaustion of critical system resources, in particular available memory (

  ENOMEM

  ), or due to attempts to exceed applicable system resource limits. A typical strategy for handling this class of error conditions is to terminate the program with a descriptive error message. More robust programs and shared libraries may wish to implement another strategy, such as retrying the operation after first letting most of the call stack unwind in order to free up scarce resources.
• Runtime errors, represented by

  lmdb::runtime_error

  . Errors of this class are thrown as a matter of course to indicate various exceptional conditions. These conditions are generally recoverable, and robust programs will take care to correctly handle them.

.. note::

The distinction between logic errors and runtime errors mirrors that found in the C++11 standard library, where the

std::logic_error

std::runtime_error

std::bad_alloc

======================== ================================ ====================== Error code Exception class Exception type ======================== ================================ ======================

MDB_KEYEXIST

lmdb::key_exist_error

MDB_NOTFOUND

lmdb::not_found_error

MDB_CORRUPTED

lmdb::corrupted_error

MDB_PANIC

lmdb::panic_error

MDB_VERSION_MISMATCH

lmdb::version_mismatch_error

MDB_MAP_FULL

lmdb::map_full_error

MDB_BAD_DBI

lmdb::bad_dbi_error

lmdb::runtime_error

.. rubric:: Footnotes

.. [4] Available since LMDB 0.9.14 (2014/09/20).

.. note::

MDB_KEYEXIST

MDB_NOTFOUND

Versioning Policy

The lmdb++ version tracks the upstream LMDB release (x.y.z) that it is compatible with, and appends a sub-patch-level version (x.y.z.N) to indicate changes to the wrapper itself.

For example, an lmdb++ release of 0.9.14.2 would indicate that it is designed for compatibility with LMDB 0.9.14, and is the third wrapper release (the first being .0, and the second .1) for that upstream target.

.. note::

To the extent that LMDB will preserve API and ABI compatibility going forward, older versions of the wrapper should work with newer versions of LMDB; and newer versions of the wrapper will generally work with older versions of LMDB by using the preprocessor to conditionalize the visibility of newer symbols--see, for example, the preprocessor guards around the definition of

lmdb::env_set_userctx()

Installation

lmdb++ is currently available as a package/port in the following operating system distributions and package management systems:

================= ============== =============================================== Distribution Package Name Installation Hint ================= ============== ===============================================

Arch Linux AUR

yaourt -Sa liblmdb++

sudo fink install lmdb++

sudo port install lmdbxx

sudo emerge --ask lmdb++

.. rubric:: Footnotes

.. [5] Still pending review.

.. [6] Compatible with Gentoo Linux, Funtoo Linux, and Sabayon Linux.

.. _Arch Linux AUR: https://aur.archlinux.org/packages/liblmdb%2B%2B/ .. _Fink: https://sourceforge.net/p/fink/package-submissions/4487/ .. _MacPorts: https://www.macports.org/ports.php?by=name&substr=lmdbxx .. _Portage: https://packages.gentoo.org/package/dev-db/lmdb++

Support

To report a bug or submit a patch for lmdb++, please file an issue in the

issue tracker on GitHub 

Questions and discussions about LMDB itself should be directed to the

OpenLDAP mailing lists 

Elsewhere

Find this project at: GitHub, Bitbucket,

Open Hub

Travis CI

Coverity Scan

.. _GitHub: https://github.com/bendiken/lmdbxx .. _Bitbucket: https://bitbucket.org/bendiken/lmdbxx .. _Open Hub: https://www.openhub.net/p/lmdbxx .. _SourceForge: https://sourceforge.net/projects/lmdbxx/ .. _Travis CI: https://travis-ci.org/bendiken/lmdbxx .. _Coverity Scan: https://scan.coverity.com/projects/4900

The API documentation is published at: http://lmdbxx.sourceforge.net/

Author

Arto Bendiken 

License

This is free and unencumbered public domain software. For more information, see http://unlicense.org/ or the accompanying

UNLICENSE