You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 22, 2022. It is now read-only.
Historically libmdbx uses the terminology (i.e. environment, database, sub-database, DBI, etc) inherited from the LMDB.
However, the terms suggested by @snej seem to me so much more successful and appropriate.
The text was updated successfully, but these errors were encountered:
Thanks 😊 I've been using those terms in my code for a while, but I hadn't proposed them for libmdbx because I figured you'd want to stay consistent with LMDB.
When learning LMDB I initially found "transaction" confusing for a read-only mode, especially since it's required for any access to keys/values.
Also, my wrapper has an OO API, with regular transactions a subclass of read-only ones, and I always find it a bad sign when a base class name is an extension of a subclass name.
For what it's worth, I adopted @snej 's terminology for the Ruby bindings. Coming from ZFS systems, "snapshot" feels the perfect term for its behavior.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Historically libmdbx uses the terminology (i.e. environment, database, sub-database, DBI, etc) inherited from the LMDB.
However, the terms suggested by @snej seem to me so much more successful and appropriate.
The text was updated successfully, but these errors were encountered: