Open alexfinnarn opened 5 years ago
I think one point to make before going into learning about more advanced SQL queries is that SQL queries can come into play when you have large databases like a CMS.
I can mention projects where I couldn't run my local machine with two sites loaded that had huge databases so I had to delete one site to work on the other.
Creating indexes and doing tuning mentioned in https://www.lynda.com/SQL-tutorials/From-declarative-SQL-procedural-execution-plan/774911/2804387-4.html should help me with those situations.
Mention that a lot of results for "sql interview questions" or "learn advanced SQL" end up going to articles with titles like "40 best questions..." or "91 things to know about SQL". These articles are pretty similar and have very simplistic explanations in them of the concepts.
I wish people would tie together the concepts better into a package of articles that you can apply to your day job...wait, maybe that's my angle here. I won't give you 40+ answers to basic questions, but I'll tell you what you need to know while actually being a full stack web developer.
I've been asked a few SQL interview questions in my day, and it always blind-sided me when it happened. I never really think about SQL queries when coding as I use some query builder and write simple queries, but I can see how more advanced knowledge would be helpful in a developer's job setting.