Support send and async send to read-only kdb instances #24
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
|
That's great! Thanks for the fix :) |
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.
Sublime currently attempts to save the result of the last input to .st.tmp, as well as using other saved helpers such as memory status (.st.mem) and start time (.st.start). The latter two can be handled just as well on the client side (in python), and the former is now made optional, thus allowing connections to be made to kdb instances where write access (i.e. creating variables in-memory) is not available. This allows sublime-q to be used with kdb processes in multithreaded input mode (negative port servers). Sublime-q is also made more efficient by reducing the number of calls made to kdb each time.