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.
This branch is actually based on my 'windows' branch, so the real diff is here:
minrk/ipython@windows...db
until PR #374 is merged
Basic features:
add HWM to Python scheduler, allowing users to tune level of job queuing. (HWM=1 behaves like old TaskScheduler, HWM=0 is default, and behaves like pure 0MQ).
DB backend changes:
db.get_history()
method (likeclient/view.history
, but returns all knownmsg_ids
)db.find_records
returns list, allows filtering of keysTwo new Client methods exposing db backends:
rc.hub_history()
# proxy for db.get_historyrc.db_query()
# proxy for db.find_recordsUp for discussion: These are Client methods, not View methods. To me, they seem like low-level methods, and thus appropriately bound to the low-level object, but They can be easily propagated up to the Views.
Extra fixes along the way:
NoEnginesRegistered
when load-balancing on all enginesrc.get_result
works with whole history if database is persistent