All of your videos are excellent. Thank you for the clear explanations and detailed examples. I hope you continue to create more videos for your channel!
Near 17:40, I think the volume table doesn’t have only one row. I think it decided to sequentially scan the volume table for each volume.volume_id will then match book.volume_id with each volume.volume_id. And for matching purposes, it is doing index scan as there is an index for book.volume_id. Sorry, I might be wrong. I didn’t understand how DBMS decided which table it will do the sequential scan first? Thanks for your video!
Hi! Thank you for explaining. The link I have in the description should give you a better understanding of how to read these query plans. I was just trying to explain the tool, rather than go into the details of how to read them.
Just wanted to say thanks for this video! This was a great step by step breakdown and analysis.
Thank you for taking the time to leave a comment. Glad you found it useful.
All of your videos are excellent. Thank you for the clear explanations and detailed examples. I hope you continue to create more videos for your channel!
Glad you found it helpful! Cheers!
Hi. Found your channel today and subscribed. Pretty good content here. Keep it up :D
Welcome aboard!
thank you it was very clear
Near 17:40, I think the volume table doesn’t have only one row. I think it decided to sequentially scan the volume table for each volume.volume_id will then match book.volume_id with each volume.volume_id. And for matching purposes, it is doing index scan as there is an index for book.volume_id. Sorry, I might be wrong. I didn’t understand how DBMS decided which table it will do the sequential scan first? Thanks for your video!
Hi! Thank you for explaining.
The link I have in the description should give you a better understanding of how to read these query plans. I was just trying to explain the tool, rather than go into the details of how to read them.
great video thanks a lot!
Glad you liked it!