Right now, catching an lmdb::error exception doesn't give much information to aid in troubleshooting incorrect uses of LMDB or runtime errors. For example, mdb_stat: Invalid argument is particularly uninformative and unhelpful. Error messages in exceptions should ideally contain some information on what the parameters passed to the underlying LMDB API function actually were.
Right now, catching an
lmdb::errorexception doesn't give much information to aid in troubleshooting incorrect uses of LMDB or runtime errors. For example,mdb_stat: Invalid argumentis particularly uninformative and unhelpful. Error messages in exceptions should ideally contain some information on what the parameters passed to the underlying LMDB API function actually were.