-
Notifications
You must be signed in to change notification settings - Fork 106
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
Use primary-key only count for Schedules B and E #4619
Conversation
42a70de
to
57ff3da
Compare
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.
Thanks for your work on this @lbeaufort -- looks good. Do you want to add anything to verify the use_pk_for_count
to test_counts.py
? I'm sure it's fine, but it probably couldn't hurt to add a simple automated test. I saw that the PR and the develop returned the same counts.
Thanks for your review, @jason-upchurch! This PR #4380 added an automated test and has some explanation of the testing approach. |
Thank you @lbeaufort! |
Download the feature branch, and tested as instructed. The queries for counting is working as expected. All tests are passed successfully. Good job!
|
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.
Look good, so approved.
Summary (required)
Use primary-key only count for Schedules B and E
Reviewers
How to test the changes locally
get_query_plan
inwebservices.common.counts.py
(Shortcut:subl webservices/common/counts.py:38
)sub_id
column instead of many columns.sub_id
column instead of many columns.Example
Impacted areas of the application
List general components of the application that this PR will affect:
Related PRs
List related PRs against other branches: