Entity Framework Core provider for PostgreSQL, enabling .NET developers to interact with PostgreSQL databases using LINQ.
Npgsql.EntityFrameworkCore.PostgreSQL is an Entity Framework Core provider that enables .NET applications to interact with PostgreSQL databases. It translates LINQ queries in C# to SQL commands, allowing developers to work with PostgreSQL using Microsoft's popular object-relational mapping framework. The provider supports both standard EF Core features and PostgreSQL-specific capabilities like JSON and array columns.
.NET developers building applications that need to interact with PostgreSQL databases, especially those already familiar with Entity Framework Core and LINQ.
It provides a fully-featured, officially-supported EF Core experience for PostgreSQL, combining the productivity of LINQ with access to PostgreSQL's advanced data types and features, all built on the reliable Npgsql ADO.NET driver.
Entity Framework Core provider for PostgreSQL
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements the complete Entity Framework Core API, ensuring a seamless and familiar experience for .NET developers, as highlighted in the README's philosophy of feeling like any other EF Core provider.
Supports unique PostgreSQL capabilities like JSON, array, and range columns through LINQ queries, allowing developers to leverage database-specific strengths beyond standard EF Core.
Offers optional plugins such as NetTopologySuite for spatial data and NodaTime for date/time, enhancing functionality with PostgreSQL's advanced types without bloating the core package.
Built on the reliable Npgsql ADO.NET provider, which handles low-level database communication, ensuring stability and performance for underlying operations.
Inherits EF Core's ORM abstraction layers, which can slow down queries compared to raw SQL or micro-ORMs, making it less suitable for latency-sensitive applications.
Full access to PostgreSQL-specific features like spatial data requires installing separate plugins, adding complexity to initial configuration and dependency management.
Dependent on EF Core's release cycle and compatibility, which can introduce breaking changes or limit flexibility during upgrades, as noted with version-specific dependencies.