Thank you so much for this. I've been battling with how the subquery works in the entire SELECT statement and I keep messing up its actual usuage, especially using the IN/NOT IN clause.
To clarify the IN and NOT IN, I think you must have only 1 column so you can treat it like a list for the IN or NOT IN. He doesn't explicitly say that, but I think that is implied.
Hands-down the best explanation of subquerying out there!!! AMAZING TUTORIAL, thank you!!! 💯👏🏼🙏🏻
Step-by-step results make this make so much sense. Thank you for clarity!
Excellent submission!🎉 bravo
Hi Dave, you have the best of the best way to explain SQL. You take the mystery out of learning SQL...
Thank you so much for this. I've been battling with how the subquery works in the entire SELECT statement and I keep messing up its actual usuage, especially using the IN/NOT IN clause.
To clarify the IN and NOT IN, I think you must have only 1 column so you can treat it like a list for the IN or NOT IN. He doesn't explicitly say that, but I think that is implied.
Great job
Great explanation !. I understand it better now
I wish i could like this video 1000 times
Dave, great video!
thanks a lot Mr. you simplified it way better than my lectures
Well explained and well done video. Thank you Dave
This is a great and very clear tutorial
perfectly explained. Thank you.
that is great teacher thank you
06:50 you could also answer this question with a join statement. Are subqueries better?
always join is effecient
Hi Sir for the second example, Find all students who are not enrolled in CS 105.
Can't it be solved with a Join?
thank you!!!
great tutorial thanks
thank you
For 6:00 , why not just do a JOIN WHERE NOT IN (12345678, 333566891) , Bad example. The reason these kids cant understand subqueries.
You mean..
where course_name != 'cs 105'
That's not a bad example. Some might prefer subquery instead of using join.
Youre at BU? Wow!
thanks pal.