this post was submitted on 27 Dec 2023
544 points (96.7% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Postgres has the
having
clause. If it didn't, that wouldn't work, as you can't use aggregates in awhere
. If you have to make do withouthaving
, for some reason, you can use a subquery, something likeselect * from (select someCalculatedValue(someInput) as lol) as stuff where lol > 42
, which is very verbose, but doesn't cause the sync problem.Also, I don't think they were saying the capability
having
gives is bad, but that a new query language should be designed such that you get that capability without it.