Feature/dynalite java jdbc #4
Open
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
Otherwise memdown will use a global store and be stateful over server instantiations Fixes architect#75
…e-ops Feature/dynalite java jdbc i/trireme ops
…velup-v2 Feature/8847/upgrade dynalite to levelup v2
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.
-Merged some fix issues and updates from mhart
-Can install with npm i --no-optional, to avoid leveldown
-Regular dynalite over leveldown still supported (you just need to run regular npm i, and when running not pass in --jdbc parameter)
-If you pass in --jdbc parameter + you run it using trireme, it will run in java and use the jdbcUrl you provided