-
Notifications
You must be signed in to change notification settings - Fork 3
Limit IDs passed to location assocations query #189
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
Open
Rovack
wants to merge
10
commits into
develop
Choose a base branch
from
feature/avoid-large-associations-query
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
346a456
feature: limit IDs passed to location assocations query
Rovack bb91275
Actually return the location stubs fetched in the 1st query
Rovack 2d37376
Fix pagination to take the updated limit into account
Rovack e39f2f1
Skip redundant plain-ification for already-raw locations
Rovack bd996a6
Actually return all fetched fields in stubs, not just IDs
Rovack d7aa7f1
Fix remaining pageSize vs. limit discrepancies
Rovack 3b92c5e
Cap minResults too (though highly unlikely to exceed 200)
Rovack 6ffc84e
Fix sorting by mostServices
Rovack bcb3f77
Restore event info to the locationFieldsOnly case
Rovack 6bc827a
Stop passing the unused Services to isLocationClosed
Rovack File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Location.searchstill uses this helper for pagination/count paths ((await ...).length), but this change replaced the oldDISTINCT Location.idprojection with a full-row select (plus extra subqueries/joins) and then deduplicates in JavaScript. On broad searches this pulls and materializes many joined rows per location just to count IDs, which can significantly increase query latency and memory use and make/locationsrequests time out under production-sized datasets.Useful? React with 👍 / 👎.