794 B
794 B
effect, @effect/sql-libsql, @effect/sql-mssql, @effect/sql-mysql2, @effect/sql-pg, @effect/sql-pglite, @effect/sql-sqlite-bun, @effect/sql-sqlite-do, @effect/sql-sqlite-node, @effect/sql-sqlite-react-native, @effect/sql-sqlite-wasm
| effect | @effect/sql-libsql | @effect/sql-mssql | @effect/sql-mysql2 | @effect/sql-pg | @effect/sql-pglite | @effect/sql-sqlite-bun | @effect/sql-sqlite-do | @effect/sql-sqlite-node | @effect/sql-sqlite-react-native | @effect/sql-sqlite-wasm |
|---|---|---|---|---|---|---|---|---|---|---|
| patch | patch | patch | patch | patch | patch | patch | patch | patch | patch | patch |
Add UniqueViolation as a new SQL error reason. Supported unique constraint violations now classify as UniqueViolation instead of the broader ConstraintError reason.
This covers PostgreSQL, PGlite, MySQL, MSSQL, and the shared SQLite classification used by the SQLite-family clients. UniqueViolation.constraint contains the best available constraint, index, or key identifier and falls back to exactly "unknown" when no reliable identifier is available.