-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
More cleaning #528
More cleaning #528
Conversation
superduperdb/core/watcher.py
Outdated
@@ -16,7 +16,7 @@ class Watcher(Component): | |||
:param model: Model for processing data | |||
:param key: Key to be bound to model | |||
:param features: Dictionary of mappings from keys to models | |||
:param active: Toggle to ``False`` to deactivate change data triggering | |||
:param enabled: Toggle to ``False`` to deactivate change data triggering |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't agree with this, since active=False
does not mean this is out of action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So what does it mean then?
"active" sounds like "it is working" == "it is enabled"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Active means that it's computing outputs every time they come in. If not active, then it still is used to watch for queries coming in, but not storing outputs in the DB.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please address the single comment.
I'm not convinced either way, so I reverted that one change. :-) |
Description
See #408.
This was just lying around in a branch. :-D