Error map
42P10 ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification
PostgreSQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
MySQL ERROR 1093 (HY000): You can't specify target table 'x' for update in FROM clause
An UPDATE/DELETE uses a subquery that reads from the same table, which MySQL doesn’t allow directly.
ERROR: currval of sequence "x" is not yet defined in this session
currval() was called before nextval() in the same session.
DbUpdateException: An error occurred while saving the entity changes. See the inner exception for details.
SaveChanges failed in the database; the inner exception (SqlException/PostgresException) has the real reason — constraint violati…
MySQL ERROR 1175 (HY000): You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
MySQL Workbench’s safe updates mode blocked an UPDATE/DELETE without a key-based WHERE.
ERROR: insert or update on table "x" violates foreign key constraint "fk" — Key (user_id)=(5) is not present in table "users"
The row references a parent row that doesn’t exist.
PostgreSQL: ERROR: duplicate key value violates unique constraint
An INSERT/UPDATE would create a duplicate in a UNIQUE or PRIMARY KEY column — or the id sequence is behind the existing data.
ERROR: update or delete on table "users" violates foreign key constraint on table "orders" — Key (id)=(5) is still referenced
You tried to delete a row that other rows still reference.
ERROR: column "x" is of type integer but expression is of type text — HINT: You will need to rewrite or cast the expression.
An INSERT/UPDATE supplies a value of a different type than the column, and PostgreSQL won’t cast implicitly.
API Error: Resource already exists (ALREADY_EXISTS / resource_already_exists / 409)
The create request was refused because an object with the same unique identity — name, email, external ID — already exists.
ERROR: could not determine data type of parameter $1
PostgreSQL can’t infer a parameter’s type from context (e.g. $1 IS NULL or SELECT $1).
ERROR: new row for relation "x" violates check constraint "y"
A value failed a CHECK constraint (e.g. price > 0, status IN (…)).
ERROR: bind message supplies 2 parameters, but prepared statement requires 1
The number of query parameters sent doesn’t match the $1, $2 … placeholders in the SQL.
Two steps away (27)
Subquery returns more than 1 row (MySQL 1242) / more than one row returned by a subquery used as an expression
A subquery used where a single value is expected (`= (SELECT …)`) returned several rows.
IncorrectResultSizeDataAccessException: query did not return a unique result: 2
A query expected one row but found several.
MySQL ERROR 1241 (21000): Operand should contain 1 column(s)
A subquery or expression returned several columns where only one is expected.
ERROR: operator does not exist: integer = text
A comparison or operation mixes types PostgreSQL won’t implicitly convert.
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
MySQL ERROR 1452: Cannot add or update a child row: a foreign key constraint fails
You inserted/updated a row whose foreign key value doesn’t exist in the referenced parent table.
JsonException: A possible object cycle was detected
System.Text.Json found a reference loop (e.g. Order → Customer → Orders → …) while serialising, usually from EF Core navigation p…
MySQL ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails
You tried to delete/update a row that other rows still reference.
ERROR: null value in column "x" of relation "y" violates not-null constraint
An INSERT/UPDATE put NULL into a NOT NULL column.
HTTP 409 Conflict
The request conflicts with the current state of the resource — e.g. a duplicate or an edit based on an outdated version.
org.hibernate.exception.ConstraintViolationException: could not execute statement
The database rejected an insert/update because of a constraint (unique, foreign key, not null).
MongoServerError: E11000 duplicate key error collection: db.users index: email_1 dup key
An insert/update violated a unique index in MongoDB.
MySQL ERROR 1690 (22003): BIGINT UNSIGNED value is out of range
Arithmetic on UNSIGNED columns produced a negative result.
ERROR: invalid input syntax for type integer: "abc"
A string couldn’t be converted to the column’s type (integer, numeric, boolean, date…).
ERROR: invalid input syntax for type uuid: "x"
A value that isn’t a valid UUID was compared with or inserted into a uuid column.
MySQL ERROR 1022 (23000): Can't write; duplicate key in table
An ALTER/CREATE produced a duplicate key or constraint name — often a foreign key name that already exists in the database.
MySQL ERROR 1048 (23000): Column 'x' cannot be null
An INSERT/UPDATE put NULL into a NOT NULL column.
PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)
A Prisma create/update violated a unique constraint.
Blue Screen: IRQL_NOT_LESS_OR_EQUAL (Stop code 0x0000000A)
A driver accessed memory at an interrupt level where that’s not allowed — almost always a faulty or incompatible driver, sometime…
Windows upgrade error 0xC1900101 (driver error, rolled back)
A Windows feature update failed and rolled back because a driver crashed or was incompatible during installation.
Blue screen: DPC_WATCHDOG_VIOLATION (0x00000133)
A driver spent too long at high priority (DPC level) — typically SSD/NVMe firmware, storage controller drivers (iaStorA.sys) or g…
API Error: Invalid type — expected integer, received string
A request field has the wrong data type — a string where the API expects a number, a number where it expects a boolean, an object…
API Error: Invalid parameter value — must be one of the allowed values / out of range
The field has the right type but a value the API doesn’t allow — not in the list of accepted options, too small or large, too lon…
API Error: Invalid date format — expected ISO 8601 (YYYY-MM-DDTHH:mm:ssZ)
A date or timestamp in the request isn’t in the format the API expects — usually ISO 8601 with a time zone, or a Unix timestamp.
ERROR: current transaction is aborted, commands ignored until end of transaction block
An earlier statement in the same transaction failed; PostgreSQL rejects everything until you ROLLBACK.
ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
Named prepared statements collided — typically because PgBouncer in transaction pooling mode hands connections between clients.
pg_dump: error: aborting because of server version mismatch
Your pg_dump client is older than the server you’re dumping.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException