Npgsql 4 has a pretty nasty bug with overflowing decimals completely breaking the connection pool though It doesn't correspond to what I know of PostgreSQL. Once again, this doesn't mean much without a very concrete case. The query compiler is just stupid compared to the SQL Server one Having moved from SQL Server to Postgres, Postgres is just painful. The one example mentioned by the author (FirstOrDefault over GroupBy) has nothing to do with the PG provider - it's a general current limitation of EF Core which is being addressed for EF Core 6.0. That really doesn't mean anything without very concrete samples. "there are some hiccups when creating queries that it doesn't translate well into sql query and you'll have to fine tune your code" NET enums as int/text in the database just like in SQL Server - but native enums are a really good feature despite some limitations. You don't have to use this feature - you can store. This refers to native enums (enum types in the database), which SQL Server doesn't support at all.
"Postgres works nice, but migrations and enum changes dont play nice!" And whether it's scalable is again more of a database question than an EF Core provider question. I'd indeed concentrate on researching which database you need for your requirements.Īgain, most of the differences are going to be differences between SQL Server and PostgreSQL as databases, rather than EF Core support for them. PostgreSQL as database" (regardless of EF or. Assuming that's true, that shifts the question to "SQL Server vs. In general, I'd consider the PostgreSQL EF Core and ADO.NET providers as mature/working/robust as the SQL Server ones - sometimes even more. This issue is a result of this discussion: dotnet/efcore#24195 I don't really have anything to add beyond what I've already written in #24195. If so, what applications is it good for? Is it scalable? What are the problems? Does EF Core work as well with Postgres as with SQL Server? similar to this list of differences in functionality between old EF 6 and different versions of EF Core.Īdditionally, I think it would be good to write an article describing whether we can easily use PostgreSQL with EF Core to build an application. In my opinion it will be good to make a list of differences in EF Core 5 support for SQL Server and PostgreSQL, e.g. "npgsql 4 has a pretty nasty bug with overflowing decimals completely breaking the connection pool though" source, 2 upvotes The query compiler is just stupid compared to the SQL Server one." source, 2 upvotes "Having moved from SQL Server to Postgres, Postgres is just painful. "there are some hiccups when creating queries that it doesn't translate well into sql query and you'll have to fine tune your code." source 1, source 2, 2-3 upvotes "Postgres works nice, but migrations and enum changes dont play nice!" source, 4 upvotes People said that Postgres support is good, but still SQL Server is supported better than Postgres.
I asked on Reddit whether Entity Framework 5 support for PostgreSQL is as good as for SQL Server.
0 kommentar(er)
