Комментарии:
Thank you very much for this video
ОтветитьGreat vid!
ОтветитьBest subquery explanation!
ОтветитьGreater and absolutely clear walk through what in backend service buildup appears to be more complex or scary.
ОтветитьWould it be possible for you to explain how to find computers that have two specific software titles installed?
Ответитьgreat tutorial, please what text editor did you use
ОтветитьThank you so much for your efforts sir !
ОтветитьSQL is so fucking boring
Ответитьhey WiseOwl, do you have a video on subqueries in the from statement? I don't understand why they work and why you would do them instead of inner joins.
Ответитьexplained a lot better than the most of the paid tutorials. Thanks posting such a nice videos and we use them thanking to you
ОтветитьAMAZING explanation!
Ответить'applause'
Ответитьvery very very very useful for me. Thanks very much
ОтветитьGreat video! thanks:D
ОтветитьHey, WiseOwl guy. In the 'Using a where clause in a subquery' section of this video, the final results left me a bit confused. The initial query used the MAX function on "FilmBudgetDollars" where the "FilmReleaseDate" is less than/before 2000-01-01, which shown that to be $200000000. So obviously nothing should be greater than the max of $200000000 before 20001-01-01, right? But then when you nested that query, turning it into a subquery, and pulling in the fields "FilmName", "FilmReleaseDate", and "FilmBudgetDollars", SQL Server some how pulled in data greater than what the MAX function initial pulled, and the data was post 2000-01-01. Why was the subquery restraints bypassed?
Edit: I just noticed the > operator in the upper query section. Ignore this post lol. Also, thanks for the great content.
Wow. Thank you. Nice contextual example. Finally getting it. Yes I am.
Ответитьthank you from germany
ОтветитьThis is a great resource ..
ОтветитьDo you have a book that cover all these chapters please? If yes how can we get this
ОтветитьNice accent!
which accent is that