Complex WHERE and HAVING aggregation condition #496
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
hrach
force-pushed
the
complex_having_where_aggregation_condition
branch
from
75f2742
to
67fac62
Compare
…se and aggretaion in HAVING This commit changes how we handle has-many relationship query construciton. Until now, every has-many relationship was simply left-joined and filtered via where. The duplication was solved by group-by statement. From now on, the joined table is filtered already in the JOIN clause and the where-part is simply aggretation count of the joined table > 0. This allow moving the where clause to having clause, where it may be combined with other aggregation filtering condition.
hrach
force-pushed
the
complex_having_where_aggregation_condition
branch
from
67fac62
to
d52f0c1
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.
No description provided.