3 ms·
If you’re using EF then just use the correct ADO.NET library and use native features - why use Babelfish with EF?
by DaiPlusPlus 5y ago
If you’re using EF then just use the correct ADO.NET library and use native features - why use Babelfish with EF?
- moron4hire 5y agoWell, in particular, the NPGSQL EF driver is pretty buggy. We frequently exhaust our connection pool and we don't even have a large database. Given the design of EF, it's difficult to see how we could possibly do anything different that would avoid exhaustion. It's a pretty vanilla setup.
- DaiPlusPlus 5y ago> Given the design of EF There's nothing about the design of EF that relates to how connections work: you can let the DbContext manage connections for you or can provide your own. (I assume you know that a DbContext is meant to be short-lived with a single owner) - so I'm very hesitant to say the issue is with EF's design or that the design of EF means you can't mitigate any issues with the PostgreSQL library for .NET. Do you have a StackOverflow or GitHub post for this? I'd like to know more about this precisely because I'm thinking of switching from Azure SQL to Postgres for its superior data-modelling features (deferred constraints!)