Don't SUCK With Entity Framework - Select * - Performance Tips Part 3

preview_player
Показать описание

► Part 3 - Select * - THIS VIDEO
In this video series, you will learn the most common performance mistakes developers do with Entity Framework. In the third part, I show why you should always include a Select statement in your LINQ queries.

★★ BECOME A BACKER OR SPONSOR ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Follow My Tested ASP.NET ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Follow Me ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Links From The Video ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
► BenchmarkDotNet:
Рекомендации по теме
Комментарии
Автор

Screamer at 12:50, watch out.
Thanks for your videos.

GorgeousPuree
Автор

If you don’t suck with EF your DBAs will be happier too!😊

ntobergta
Автор

Thank you Ivo, just want to point out that the last few videos have really low microphone sound (including this too), keep going

georgimutafov
Автор

Is there a difference if I use the 'Cat' class instead of the 'CatResult' class in the select part?

TheDimiccC
Автор

Can I modify the Age of Cat if I retrieve them to CatResult in this way? Will ef core track changes to CatResult and save to Cat table?

randomshorts
Автор

Sounds like this is something that the EF provider should take care of by looking at the fields used in ToDictionary()

Eirenarch
Автор

This dude ( shayankamalzadeh medium) use your video to create this article ( ), moreover, he use your example. He copy-paste :-)

FedorenkoV