☆ Yσɠƚԋσʂ ☆@lemmy.ml to General Programming Discussion@lemmy.mlEnglish · 1 year agoI Don't Need Your Query Languageantonz.orgexternal-linkmessage-square3fedilinkarrow-up18arrow-down14cross-posted to: hackernews@lemmy.smeargle.fans
arrow-up14arrow-down1external-linkI Don't Need Your Query Languageantonz.org☆ Yσɠƚԋσʂ ☆@lemmy.ml to General Programming Discussion@lemmy.mlEnglish · 1 year agomessage-square3fedilinkcross-posted to: hackernews@lemmy.smeargle.fans
minus-squarezepplenzap@lemmy.sdf.orglinkfedilinkEnglisharrow-up1·edit-21 year agoIt has been years since I wrote any SQL, so I may just be missing something but: Why is the “As it could be” example for the second example using sub selects?! Especially the one in the where clause where they are selecting two tables that they already joined in the from clause? And wouldn’t it be quicker to join the review table and use a group by?
minus-square☆ Yσɠƚԋσʂ ☆@lemmy.mlOPlinkfedilinkEnglisharrow-up1arrow-down2·1 year agoI think the example is trying to optimize for readability to show that it can be pretty intuitive, but I think you’re right.
It has been years since I wrote any SQL, so I may just be missing something but:
Why is the “As it could be” example for the second example using sub selects?!
Especially the one in the where clause where they are selecting two tables that they already joined in the from clause?
And wouldn’t it be quicker to join the review table and use a group by?
I think the example is trying to optimize for readability to show that it can be pretty intuitive, but I think you’re right.