Move DestroyDB call from erlang thread to background thread. #142
Conversation
This file contains 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
| destroy_int(_Name, _Opts) -> | ||
| erlang:nif_error({erlang, not_loaded}). | ||
| CallerRef = make_ref(), | ||
| Opts2 = add_open_defaults(Opts), |
There was a problem hiding this comment.
I imagine you don't need the default open opts here, but was just a cut n' paste addition?
There was a problem hiding this comment.
The DestroyDB call does require leveldb::Options structure as a parameter (that is same as open_options here).
…lure return value
|
+1 1d5c32a Code looks good now, tests pass. I confirmed the interface is now the same after the last fix. S'all good. |
matthewvon
added a commit
that referenced
this pull request
Jul 2, 2015
Move DestroyDB call from erlang thread to background thread.
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.
No description provided.