Experiment... As the "search engine" behind a 5000-records auto complete API is an #efcore LIKE query. Loading 60000 more records into that table made the API endpoint slow (6 seconds to show autocomplete!)
I wanted to do some work on #efcore#efcore8 provider for #Firebird#firebirdsql, but I'm so tired. I'm tired last couple of weeks. And everything is getting behind, increasing my anxiety.
Yesterday was my first day in #efcore team (moving from .NET performance). If #efcore 9 becomes awesome, you know why. If not, it wasn't me, I'm new here.
#EFCore users, how do you feel about using #dotnet 8 C# language features instead of DataAnnotation attributes?
On the one hand, I like that it reduces noise. On the other hand, you will likely have a mix of attributes and C# language features, which can lead to mental context switching.
Hi #dotNET developers,
in case you have already upgraded to #Npgsql 8.0 and are affected by a bug, you may be happy that Npgsql 8.0.1 has been released.
See https://github.com/npgsql/npgsql/milestone/110?closed=1 for the issues that have been closed in this release. #NpgsqlEFCorePG the corresponding #EFCore provider has not been released yet but the existing release should be compatible with Npgsql 8.0.1
Entity Framework Core, or any ORM for that matter, can be magic, madness and maybe even a sin. Come to my workshop so your following project is not your next mistake. I'll show you incredible things, leave you breathless (and without scars), possibly screaming and crying.
In this post, we explore the different ways of loading related data using #EntityFrameworkCore, and what the advantages and drawbacks of each approach are.