Merged
Conversation
EB-4012 added whereIn function and unit test
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
2 participants
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.
In postgres, a WHERE OR statement will take a considerable amount of time to process a query containing many args. Up to 15 minutes in our tests for 15k db entities. Most of this came from the query optimisation stage, and after that stage the db chose to search the table sequentially which is very slow.
Using a WHERE IN statement, foreign key tables are joined, resulting in a query execution time of ~90ms for 15k entities.
More information about this speed increase can be found here: https://stackoverflow.com/questions/68484681/why-in-is-so-much-faster-than-in-sql-select