Thank you for the video it really showed me how the python functions / commands actually work in the real world. Question you probably explained 20 times and I didn’t capture it, why did the SQL keep making the same entries (duplicating), is it because you purposely didn’t add a command in the SQL script to prevent that from happening? Thanks
Hello! Thank you for watching and for the nice comment - yes you can add a check to make sure every line of SQL data is unique before adding a duplicate - SQL uses a keyword DISTINCT to basically check for uniqueness, it’s just a little beyond the scope of a beginner tutorial!
Hey nice optimization! I try to gear these videos towards being clear and helpful to beginner/intermediate folks too so I just try to write it to be very clear and easy to understand, but your way is very nice and smooth!
@@lemastertech doing len() checks for iterating over nested lists might make people coming from c/java world more comfortable, but it won't really make it easier for people new to programming and it's just not idiomatic python at all. Consider that, to a novice, iterating like that and then accessing arrays over 2 dimensions looks like word salad. Yes it's true that iterable unpacking is 'one more special thing' for people to learn but it's a must use if you want code to read like natural English (and if you don't want that, why even use Python?). Plus I'm pretty sure people instinctively would understand unpacking here, whereas in the original version they'd have to decipher a bunch of nested function calls and data (btw if you really need the index, just use enumerate). Ultimately not using the idioms of the language makes for a greater disservice than not being clear enough (and in that process of trying to be verbose you can easily murk things up instead of making them clearer). I only commented about this because I saw you do this in other videos too. You should write idiomatic Python that reads as close to English as possible, and take some time to explain when you inevitably end up using Python specific features (e.g. unpacking, context managers).
You are a legend. More more more tutorials please.
Thank you so much!! I’m always trying to keep new useful content coming out!
Interesting 😊
Thanks Philip!
Thank you
You’re welcome thanks for watching!!
More sql please :D
Thanks for the feedback!! I’ll plan on doing some more SQL tutorials soon then! :)
my g
My G
first comment!
Thanks for being here!
Thank you for the video it really showed me how the python functions / commands actually work in the real world.
Question you probably explained 20 times and I didn’t capture it, why did the SQL keep making the same entries (duplicating), is it because you purposely didn’t add a command in the SQL script to prevent that from happening?
Thanks
Hello! Thank you for watching and for the nice comment - yes you can add a check to make sure every line of SQL data is unique before adding a duplicate - SQL uses a keyword DISTINCT to basically check for uniqueness, it’s just a little beyond the scope of a beginner tutorial!
Not so much into databases but good to know anyways.
hey you never know when it could come in handy haha! I have to do this all the time for work so it seemed like a good lesson
@@lemastertech It definitely is useful, cheers!
👍👍🙏🙏
Glad you liked it!
8:57 "for video in videos: name, views, date = video"
Hey nice optimization! I try to gear these videos towards being clear and helpful to beginner/intermediate folks too so I just try to write it to be very clear and easy to understand, but your way is very nice and smooth!
@@lemastertech doing len() checks for iterating over nested lists might make people coming from c/java world more comfortable, but it won't really make it easier for people new to programming and it's just not idiomatic python at all. Consider that, to a novice, iterating like that and then accessing arrays over 2 dimensions looks like word salad.
Yes it's true that iterable unpacking is 'one more special thing' for people to learn but it's a must use if you want code to read like natural English (and if you don't want that, why even use Python?). Plus I'm pretty sure people instinctively would understand unpacking here, whereas in the original version they'd have to decipher a bunch of nested function calls and data (btw if you really need the index, just use enumerate).
Ultimately not using the idioms of the language makes for a greater disservice than not being clear enough (and in that process of trying to be verbose you can easily murk things up instead of making them clearer). I only commented about this because I saw you do this in other videos too.
You should write idiomatic Python that reads as close to English as possible, and take some time to explain when you inevitably end up using Python specific features (e.g. unpacking, context managers).
Im interested in more sql
Thanks for the feedback!! I’ll plan on doing some more SQL tutorials soon, thanks for watching!