3 ms·
What if you're not looking for an experienced data modeller, but someone who can write SQL? Also: If you can read the SQL book two days earlier and answer thes
by pessimizer 13y ago
What if you're not looking for an experienced data modeller, but someone who can write SQL?
Also: If you can read the SQL book two days earlier and answer these questions in a reasonable amount of time - sounds like an insta-hire to me. There's certainly nothing so hard about SQL that you couldn't do that - but some people who spend a lot of time working with databases seem to find the climb insurmountable.
- jacques_chester 13y agoWhen I learnt SQL, the part that took me the longest to square away was the distinction between WHERE and HAVING. It was thoroughly confusing at the time. Once you grasp that conceptually, SQL generally executes left-to-right, it's easier.
- siddboots 13y agoI avoid `having` wherever possible these days. There are data analysts in my team that I know would have to think twice about it if they encountered it in my code, and to be honest, it's a bit of an wart in the SQL grammar anyway. In (almost) all cases, a subquery with an extra `where` clause will have equal performance to a `having` clause in the main query. See the final example in: http://en.wikipedia.org/wiki/Having_(SQL) http://en.wikipedia.org/wiki/Having_(SQL)