3 ms·
> I would call it a layman issue SQL beginners learn the hard way. Advanced SQL users know the very basics of the db they are working with. So? Does every blo
by ncallaway 6y ago
> I would call it a layman issue SQL beginners learn the hard way. Advanced SQL users know the very basics of the db they are working with.
So?
Does every blog post have to be for expert users of the system? What's wrong with a blog post that explains mistakes that a beginner might make, and a method for mitigating it.
- kroolik 6y agoCompletely nothing is wrong with it! That's not what I'm arguing with. I'm challenging the statement in the Conclusion section: > Arriving at query #2 to get the combined results was the intuitive way of thinking through the problem, and something that someone with intermediate or advanced SQL skills could come up with. The issue in question is simple. It's a very good lecture for people early in their SQL journey. It would be a superb read if the author had dug into the details why it's slow. But advanced engineers should know that LEFT JOINing 6+ tables will be huge. I disagree it's a mistake an experienced person would do.
- ncallaway 6y agoAh, fair play. I must’ve missed that part of the article, or just didn’t have it top of mind when reading your comment.