Тэги:
#becoming_a_data_scientist #becomingads.com #data_science #data_scientist #sql_with_statement #postgresql_with_statement #sql_cte #postgresql_cte #sql_common_table_expression #postsgresql_common_table_expressionКомментарии:
Thank you
ОтветитьThank you. It was wonderful explanation
ОтветитьI don't understand what the ctdorders have inside...
ОтветитьHow can I union two cte together, there is one sum on a budget, column are exactly the same I have group by , send me video please
ОтветитьCan I pass list of acctnumbers in with and it will traverse through each one of them to fetch acctid from diff table
ОтветитьThanks a lot for simple explanation
ОтветитьDude! thank you for taking the time to break down cte's simplified (subquery >> cte). Bro, you rock!!! 😎🤟
ОтветитьI don't see the point of using WITH for a single query. If you would use the same WITH for multiple queries, I can understand how it helps.
ОтветитьThank you! This video helped me understand CTEs a little bit better.
Ответитьin the 3rd example nothing changed when you joined another cte. So why did you join them?
ОтветитьThanks! Liked, Commented and Subscribed!
ОтветитьThanks, mate! Your explanation is very easy to understand.
ОтветитьBest explanation ever!! 👍
ОтветитьVery helpful..... Love from India
Ответитьconceptual and easy way to describe
Ответитьand, boom!
Ответитьwhy did you use "using" in your join statement and not "on"?
ОтветитьThank you for the video, very clear, I like the format, it's straightforward and very well explained!
Ответитьhello there, god bless your efforts..I have a simple enquiry as new sql learner.
How are CTEs different from temporary tables?
Thanks for taking care of this.
Great explanation
ОтветитьThank you for this very useful video!
ОтветитьI've been studying SQL now for about 6 months....I think the CTEs are really a good place to start but the more knowledge you gain the more you tend to move away from them and use subqueries
ОтветитьGreat video! This helped me run a complex query at work. Thanks 😀
ОтветитьSweet and simple: thanks!
ОтветитьThanks, easy and straight forward!
ОтветитьNice video, thank you
ОтветитьThe way you describe what cte's are made all the difference. It's so simple when you know yhe why for the how.
ОтветитьJust a small correction, using the with statement makes indeed things easier to read and debug but the program won't be any faster. It's just a thing you should do to help other humans understand your code.
ОтветитьHi Nathan, thanks for explaining me CTE Objects. It's know very clear to me. Appriciate <3.
ОтветитьI didn't think CTE's are stored anywhere... temp tables are
ОтветитьYou have a crypto channel too?! I have seen your YF vids
Ответитьthankyou sir, it really helped me.
ОтветитьGreat video!
Ответитьhats off!!
ОтветитьSuper sir 👍👍👍
ОтветитьSimple and easy to understand explanation. It really made understanding the WITH statement so simpler. Thanks much.
ОтветитьWhy the pc screen is so blurred?
ОтветитьThanks!
ОтветитьThanks for the video. I was looking for more info about caching, but noticed (after some reading) that the caching doesn't happen because of the CTE, but instead, it's decided arbitrarily by Postgres. So for instance, either doing subqueries or CTEs might result in the same performance in the end, even though CTEs makes code more readable.
ОтветитьThat was super helpful!
Ответитьahhh That makes it much clearer. Thank you!
Ответитьwhat is the difference between cte:s and temp tables? temp tables are only stored temporarly and cant be accessed as an cte?
ОтветитьThis is clearer than my textbook explanation lol thanks for the video!
ОтветитьThanks! That was very helpful :)
ОтветитьExcellent explanation . How dose work when you're working with 10 tables and 5 has millions of records in them? Is this viable considering this is all done in memory?
Thanks
Definitely helpful! Thank you for this. Can you also do a video on recursive CTEs?
ОтветитьThis is great!
ОтветитьYou explained it so well and fast I'm now fully prepared for what may come
Ответить