[WV-2618] queryset_find_possible_duplicate_candidates_to_merge_with_this_candidate inefficient query [Team Review]#3058
Merged
DaleMcGrew merged 4 commits intowevote:developfrom Apr 16, 2026
Conversation
queryset_find_possible_duplicate_candidates_to_merge_with_this_candidate inefficient queryqueryset_find_possible_duplicate_candidates_to_merge_with_this_candidate inefficient query [Team Review]
Contributor
|
Seems good! |
Member
|
👍 |
This file contains hidden or 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
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.
What github.com/wevote server/issues does this fix
WV-2618
queryset_find_possible_duplicate_candidates_to_merge_with_this_candidateinefficient queryChanges included this pull request?
candidate/controllers.pyAdded trigram-based query support to improve SQL query performance. If trigram indexes are unavailable, the original query is used as a fallback so results are still returned.
**Note: **This PR should be reviewed and executed together with the following PRs:
#3055
— Needed to show trigram vs. non-trigram search results.
#3054
— Generates the required trigram indexes for improved SQL query performance.