# Giorgi/EntityFramework.Exceptions

Strongly typed exceptions for Entity Framework Core. Supports SQLServer, PostgreSQL, SQLite, Oracle and  MySql.

Repository: https://github.com/Giorgi/EntityFramework.Exceptions
Canonical: https://ross.abutalabs.com/products/entityframeworkexceptions
Homepage: https://giorgi.dev/entity-framework/introducing-entityframework-exceptions/
Language: C#
License: NOASSERTION
License Family: other
Topics: entity-framework-core, netcore2, sql-server, postgresql, mysql, netcore3, database-exceptions, sqlite, sqlite3, entityframework, entity-framework, odp-net, oracle, orm, dotnet-core
Last push: 2026-03-29T19:42:55+00:00

## Health v2 (maintenance only)
Score: 66/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 74, release rhythm 35, longevity 100
- inputs: {"age_days": 2836, "days_push": 157, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1735, forks 83 (observed 2026-08-28T04:05:29.079577+00:00)

## What it is
A .NET library that converts Entity Framework Core's generic DbUpdateException into strongly typed exceptions like UniqueConstraintException and CannotInsertNullException. It supports SQL Server, PostgreSQL, SQLite, Oracle, and MySQL by handling database-specific error details.

## Use cases
- handle unique constraint violations in EF Core without parsing error numbers
- catch null insert errors with typed exceptions
- distinguish max length exceeded errors from other database failures
- write database-agnostic exception handling across SQL Server, PostgreSQL, MySQL, SQLite, and Oracle
- simplify error handling when saving changes with Entity Framework Core

## When to choose
- you use Entity Framework Core and need to react to specific constraint violations
- you want database-agnostic typed exceptions instead of vendor-specific error codes
- you support multiple database providers and want uniform error handling

## When to avoid
- you use raw ADO.NET or a micro-ORM like Dapper instead of EF Core
- you only need generic failure handling and don't care about the cause
- you use a database provider not among the supported five

## Facets
- artifact type: library
- maturity: active
- function: orm, error-handling, database
- domain: databases, developer-tools, backend
- platform: dotnet, cross-platform
- tags: entity-framework-core, strongly-typed-exceptions, sql-server, postgresql, mysql, sqlite, oracle, dbupdateexception

## Member repositories
- Giorgi/EntityFramework.Exceptions (main) score 66

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:29.079577+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:30:43.425244+00:00, confidence not recorded.
  - readme: https://github.com/Giorgi/EntityFramework.Exceptions (fetched 2026-08-28T04:05:29.079577+00:00, sha 38c0dc6360dd)
  - homepage: https://giorgi.dev/entity-framework/introducing-entityframework-exceptions/ (fetched 2026-08-29T11:07:55.641030+00:00, sha f3eda04e4575)
- Data as of 2026-08-30T08:39:29.467469+00:00.