Add is_requested property to schedule endpoints #840
Merged
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
benoit74
force-pushed
the
add_is_requested
branch
from
95657c7 to
4e8b83b
Compare
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.
Rationale
Fix #720
Changes
is_requestedproperty onGET /schedules/andGET /schedules/{schedule_name}endpointsGET /schedules/, property is computed based on an addition to the complex SQL Query retrieving schedules and their propertiesGET /schedules/{schedule_name}, property is computed based on an additional SQL Query (transparent) to retrieve requested_tasks of current schedule (not an issue since we have only one schedule and rarely a requested_task)GET /requested_tasksendpoint anymore, column is sourced directly fromis_requestedproperty