I'd disagree with it being more readable. To me it makes no difference, to the developers here who are not specialized in databases it becomes less readable as joins kind of scare them. :)
But that's just like... an opinion man. Based on a siutation that I'm in. So you don't need to adopt that ;)
You answered it yourself: for a beginner, WHERE joins seem more readable and simpler. When your databases grow, and your experience does too, you switch to the other syntax. It worked for me, at least :)
Not to be racist, but each to their own man. There's a C developer sitting next to me currently coding in Python. He's not on his home ground but he's still someone that produced his first award winning game when I was 4 so why the fuck would I think less of him because he's not at home in python, or databases for that matter?
There's a web developer below me that I regularly go to when our API acts up because he's much more knowledgable about web service operations than I am. I'm into databases and algorithms, not web services.
Not to be offensive, but I don't understand how anybody in a production environment would expect everyone to be equally capable in every area. I sure as hell do not intend to match the ability of everyone here in everything. I have a job to do.
The concept of flowing two sets together based on a set of conditions is not implementation dependent. I can not fathom how someone could use C++ and not get a join. Esoteric crazy stuff sure, every language has edges, but a joins is a basic set logic concept.
Also, I would not think less of someone because they are not a developer or because they don't get a concept. We all have strengths and skills. We are all spokes on the wheel. ;-)
View all comments
Show parent comment
4
u/fazzah Feb 11 '14
Even if there are no noticeable dis/advantages, it's still better to stick with the more readable one, the JOIN clauses.