zlacker

[parent] [thread] 2 comments
1. andy80+(OP)[view] [source] 2024-08-24 18:20:20
If you perform an aggregation query in a CTE, then filter on that in a subsequent query, that is different, because you have also added another SELECT and FROM. You would use WHERE in that case whether using a CTE or just an outer query on an inner subquery. HAVING is different from WHERE because it filters after the aggregation, without requiring a separate query with an extra SELECT.
replies(1): >>RaftPe+Hm
2. RaftPe+Hm[view] [source] 2024-08-24 21:21:58
>>andy80+(OP)
> HAVING is different from WHERE because it filters after the aggregation, without requiring a separate query with an extra SELECT.

Personally I rarely use HAVING and instead use WHERE with subqueries for the following reasons:

1-I don't like repeating/duplicating a bunch of complex calcs, easier to just do WHERE in outer query on result

2-I typically have outer queries anyway for multiple reasons: break logic into reasonable chunks for humans, also for join+performance reasons (to give the optimizer a better chance at not getting confused)

replies(1): >>sgarla+OQ1
◧◩
3. sgarla+OQ1[view] [source] [discussion] 2024-08-25 13:54:17
>>RaftPe+Hm
The main (only?) task I routinely use HAVING for is finding duplicates.
[go to top]