Add support for listing Dbi flags #146
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8809f8e to
fed0c5d
Compare
|
Thanks for this PR. |
benalexau
added a commit
that referenced
this pull request
Apr 15, 2020
benalexau
added a commit
that referenced
this pull request
Apr 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added support for the
mdb_dbi_flagscall. We are using this in our project to inspect which flags a Dbi was created with. In particular we have a piece of code to copy an entire DB re-writing the keys in an ordered fashion to reduce wasted space (within the pages). For this we need to know what flags the new DB needs creating with and if we need to setMDB_APPENDorMDB_APPENDDUPwhen inserting into our copied DB.