You are the best instructor in the field of programming based on my experience, I wish I had a professor like you when I studied CE at University. I can not help but admire your natural talent to simplify complex concepts.
In my junior dev job, they were using different places interechangeably these two collection types: IEnumerable & IQueryable. And I was very confused with the requirement of doing such implementation. You have clarified my doubts and questions. And it makes a big difference of using the two different types of collections when we are mutating the various different objects. Thank you so much for taking the effort and time to deliver such essential information.
Great video with the answer on the question! I failed an interview the other day due to some failed answer attempts, one of which was about the difference between IEnumerable and IQueryable...
Might be worth noting that the delay in querying the database could lead to adverse results if there are table changes between creating the interface and applying the filter. Good video though
Excellent video. Very simply explanation of the differences between IQueryable and IEnumerable with EF. Quick question though... if you applied a ToList() on the end of where you called dal.Employees so it was dal.Employees.ToList(), would all calls now be in memory? So would you only have gone to the DB once to load the Employees table and then all filters are just applied to the in memory list? Thank you.
Hi Shiv, Your videos are very good to understand the concepts. In one of the interviews, along with this difference I was asked which one is having thread safety feature or thread safe. I couldn't answer it properly. I tried to search on net but didn't get proper answer. Can you help me to get this answer so it will help me to clear that concept. Thanks
Great video as always. Of course an example of in memory would have been nice too. If we have an in memory list and we use iqueryable instead of ienumerable, do we get any drawbacks?
I think it is missed that depending on what indexes exists on the table in database. Iquariable is not allways the better choise in a high performance volume environment. So many times it is better to hit indexes and pull that data, then to the filtering on client side
Hello Sir, I have one question. We have 2 options to get data from DB using EF ie. List data = _context.tableName.AsQueryable().Where(x => x.id == 33144).ToList(); and List data = _context.TableName.Where(x => x.id == 33144).ToList();. Both have same impact when we see in SQL profiler then why to use IQueryable?
Another use case would be to add filters on run time, for example in your query if there is one more parameter lets say as name, so if name filter needs to be applied based on condition, then also you can use IQuerayable
Very Nicely Explained it sir, But I have one small query regarding IQueryable, may be it is silly question (don't mind)..!! If I am declaring IQueryable variable and initializing (getting data from DB) Apply where conditions and filter the data, and in next line I am getting a count() of that variable then there will be 2 DB call (1st for getting data with filtered and 2nd for getting count(*)) or only 1st DB call..?? Ex: IQueryable results = db.GetTable().Where(Expression); var recordList = results.ToList(); int totalRecords = results.Count(); Please help..! Thank you in advance..!!
30 Important C# Interview Questions : ua-cam.com/video/BKynEBPqiIM/v-deo.html
Software Architecture Interview Questions : ua-cam.com/video/AtTgcbLOqMM/v-deo.html
25+ OOPS Interview Questions : ua-cam.com/video/u99wAoBjDvQ/v-deo.html
20+ SQL Server Interview Questions : ua-cam.com/video/SEdAF8mSKS4/v-deo.html
10+ Power BI Interview Questions : ua-cam.com/video/Cozc9WNBRt4/v-deo.html
20 MSBI Interview Questions : ua-cam.com/video/Nw_sHEKnOUE/v-deo.html
SQL Server Joins : ua-cam.com/video/KTvYHEntvn8/v-deo.html
SQL Step by Step - ua-cam.com/video/uGlfP9o7kmY/v-deo.html
Angular Step by Step Tutorial for Beginners : ua-cam.com/video/-9VcW7MBDs8/v-deo.html
25 Angular Interview Questions : ua-cam.com/video/-jeoyDJDsSM/v-deo.html
25 Important ASP.NET Interview Questions : ua-cam.com/video/pXmMdmJUC0g/v-deo.html
35 Important JavaScript Interview Questions : ua-cam.com/video/Zb4dPi7CANU/v-deo.html
20 MySQL Interview Questions : ua-cam.com/video/9hfjC-BpY20/v-deo.html
5 MSBI Interview Questions : ua-cam.com/video/5E815aXAwYQ/v-deo.html
20 PHP Interview Questions : ua-cam.com/video/1bpNSynUrl8/v-deo.html
Straight to the point, you answered the question and visually showed the effects of using IQueryable using the profiler. Very well done!
You are the best instructor in the field of programming based on my experience, I wish I had a professor like you when I studied CE at University. I can not help but admire your natural talent to simplify complex concepts.
In my junior dev job, they were using different places interechangeably these two collection types: IEnumerable & IQueryable. And I was very confused with the requirement of doing such implementation. You have clarified my doubts and questions. And it makes a big difference of using the two different types of collections when we are mutating the various different objects. Thank you so much for taking the effort and time to deliver such essential information.
Thank you. This 7-minute video indirectly answered a question I've been trying to find an answer to for a while. Subscribed. 🎉
Great video with the answer on the question! I failed an interview the other day due to some failed answer attempts, one of which was about the difference between IEnumerable and IQueryable...
This channel is one of the most underrated channels in youtube.
Excellent explanation within a very short time.
awesome bro.. can't say thank you enough to all youtube teachers .. Happy 2019
Awesome sir. You are great. Nicely explained the topic and very easy to understand the difference. Please keep your awesome teaching.
Thanks
I've been looking for this kind of video for a couple of hours already. great job!
❤ 😮 wow thats awesome! This can be a huge performance hindrance
Great video, i was always confused to these concept. but today i am fully clear on this concept.
Awesome way of showing the difference. That's what I like in your content
Great One... Superb Exlpaination.
Thank You Sir It helps a lot 😍.. Good information
Short and sweet yet taught ME the difference! Thank you!!!
Really cleared explanation in simple words.
Thank you so much for this explanation! God bless
Awesome... what an explanation.. Thank-you sir
I like the way you explain these topics in all your videos.
very clear explained, nailed it
Perfect! Great video! Very useful for deciding to use both interfaces. Thank you!
Super great explanation! Clearly understandable! Thanks!!! Keep up your good teaching
I really see awesome practical example. thanks a lot sir.
Sir you are great. Very useful video. Thanks a lot!!
Great explanation 👍
It's really very helpful for me...
Might be worth noting that the delay in querying the database could lead to adverse results if there are table changes between creating the interface and applying the filter. Good video though
if there are table changes, and if IQueryable doesn't work, most likely even IEnumerable won't work.
Explanation was awesome
Great explanation. Thanks!
Good video ! Simple and concrete answer.
This video was awesome, straight to the point!
Very nice explanation bro, thank you
Excellent video. Very simply explanation of the differences between IQueryable and IEnumerable with EF.
Quick question though... if you applied a ToList() on the end of where you called dal.Employees so it was dal.Employees.ToList(), would all calls now be in memory? So would you only have gone to the DB once to load the Employees table and then all filters are just applied to the in memory list? Thank you.
Hi Shiv,
Your videos are very good to understand the concepts.
In one of the interviews, along with this difference I was asked which one is having thread safety feature or thread safe.
I couldn't answer it properly. I tried to search on net but didn't get proper answer. Can you help me to get this answer so it will help me to clear that concept.
Thanks
Very excellent explanation...
Thank you for your great explanation.
Very clear explanation. Thank you.
Great explanation sir. Thank you so much.
what a nice tutorial sir ji,great
Great video as always. Of course an example of in memory would have been nice too. If we have an in memory list and we use iqueryable instead of ienumerable, do we get any drawbacks?
Thanks a lot ,This is the best advice in my day.
Good show and crystal clear
Brilliant 👍
Great explanation and information, thank you!
Thanks bro! keep uploading useful information like this!
I think it is missed that depending on what indexes exists on the table in database.
Iquariable is not allways the better choise in a high performance volume environment. So many times it is better to hit indexes and pull that data, then to the filtering on client side
Very nice explanation, Great man!, thank you so much!
Very good example.
Thank you for the feedback.
Your amazing thank you.
Its good for me
great sir
Well explained, thanks
Thanks for good explanation!
I have interview tomorrow..hope this one helps
Just prepare this video you should be able to answer 15% of the interview questions ua-cam.com/video/BKynEBPqiIM/v-deo.html
Nice video. To the point. No BS
You are awesome 😎
Unique Explaining
Now clear... Love it.
VERY useful video.
You are great, Sir!
Hello Sir, I have one question. We have 2 options to get data from DB using EF ie. List data = _context.tableName.AsQueryable().Where(x => x.id == 33144).ToList(); and List data = _context.TableName.Where(x => x.id == 33144).ToList();. Both have same impact when we see in SQL profiler then why to use IQueryable?
Another use case would be to add filters on run time, for example in your query if there is one more parameter lets say as name, so if name filter needs to be applied based on condition, then also you can use IQuerayable
Very Nicely Explained it sir,
But I have one small query regarding IQueryable, may be it is silly question (don't mind)..!!
If I am declaring IQueryable variable and initializing (getting data from DB) Apply where conditions and filter the data, and in next line I am getting a count() of that variable then there will be 2 DB call (1st for getting data with filtered and 2nd for getting count(*)) or only 1st DB call..??
Ex:
IQueryable results = db.GetTable().Where(Expression);
var recordList = results.ToList();
int totalRecords = results.Count();
Please help..!
Thank you in advance..!!
Thanks for making clear understanding, Please make video on visual studio 2019 tools, its features, tips & hidden tricks etc.
Excellent
good example, suggestion work more on speech it will become great
Brilliant. Thanks a lot.
Worth to watch
Thank you so much for this !
tnx, man! It was really good video and good explaining different between IEnumerable and IQueryable!!! Like!
Nice. well explained !. can't we filter while loading Employee table or using linq ?
Good explaination
Love this video
Thank You :)
Thank you!
Thank you very much
nice and informative. Thanks
awesome sir
Many thanks man.
nice video, great information
Great video adds more insight into collections.
Sir please make interface video
Please 🙏
Our video on Abstract class & Interfaces you can watch below :-
ua-cam.com/video/0EnSPBVrbG0/v-deo.html
Can i get referral for .net developer fresher opening!??
Good stuff.
Many thanks
This is neat.
Best video
At the starting of the video you have shown us the playlist where we'll get those videos??
visit www.questpond.com
In simple words, using Iqueryable will defer query execution..
yes sir , but until we do not see it , simple words are not simple :-) happy learning.
Thanks
Great.......
Super sir
Perfect
Thank you sir..
thanks for this vid
Understand sir
Thanks a lot !!!
If I remember IEnumerable uses expression tree and IQueriable uses tree traversial.
Nice
Super
Hi sir, but I thought interfaces are abstract and don't contain any logic then how are the differences highlighted in the video work.
Interfaces are pointing to a list or some concrete collection
Thank you. Can you point out a resource where I can get this type of info?