Error map
42701 ERROR: column "x" of relation "y" already exists
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)
Rails: ActiveRecord::PendingMigrationError — Migrations are pending. To resolve this issue, run: bin/rails db:migrate
The database schema is behind the migration files in the app.
ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
Named prepared statements collided — typically because PgBouncer in transaction pooling mode hands connections between clients.
ERROR: database "x" is being accessed by other users — There is 1 other session using the database.
DROP/RENAME DATABASE can’t run while other sessions are connected.
dotnet ef: Unable to create a 'DbContext' of type ''. The exception 'Unable to resolve service for type DbContextOptions' was thrown while attempting to create an instance
dotnet ef migrations couldn’t construct your DbContext at design time.
MongoDB: MongoServerError: Document failed validation (code 121)
The collection has a JSON Schema validator and the inserted/updated document doesn’t satisfy it.
PostgreSQL: ERROR: relation "x" does not exist
The table/view isn’t found — missing migration, wrong schema, or a case-sensitive quoted name.
MySQL ERROR 1146 (42S02): Table 'db.table' doesn't exist
The query references a table that MySQL can’t find in that database.
PostgreSQL: ERROR: column "x" does not exist
PostgreSQL can’t find the column — a missing migration, a case-sensitive quoted name, or a string literal written in double quote…
ERROR: relation "x" already exists
CREATE TABLE/INDEX/SEQUENCE used a name that already exists in that schema.
API Error: Request failed schema validation (must NOT have additional properties / Additional properties are not allowed)
The JSON body doesn’t match the endpoint’s schema — an unknown property, wrong nesting, or a missing required object.
MySQL ERROR 1060 (42S21): Duplicate column name 'x'
A CREATE/ALTER adds a column that already exists, or a SELECT in a view/derived table produces two columns with the same name.
ERROR: cannot drop table x because other objects depend on it
Views, foreign keys or other objects depend on what you’re dropping.
Two steps away (32)
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 1051 (42S02): Unknown table 'x'
DROP TABLE targeted a table that doesn’t exist.
MySQL ERROR 1061 (42000): Duplicate key name 'x'
CREATE INDEX/ADD INDEX used an index name that already exists on the table.
HikariPool-1 - Connection is not available, request timed out after 30000ms
The connection pool was exhausted — all connections were busy for 30 seconds.
ERROR: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
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.
LOG: could not bind IPv4 address "0.0.0.0": Address already in use — Is another postmaster already running on port 5432?
Another process (often a second PostgreSQL install or a container) already listens on 5432.
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.
InvalidOperationException: Unable to resolve service for type 'X' while attempting to activate 'Y'
ASP.NET Core’s dependency injection container can’t build Y because one of its constructor dependencies (X) was never registered.
MySQL ERROR 1091 (42000): Can't DROP 'x'; check that column/key exists
ALTER TABLE tried to drop a column or index that doesn’t exist.
Laravel: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'db.sessions' doesn't exist
Laravel queried a table that hasn’t been created — usually sessions, cache, jobs or a new model’s table.
MySQL ERROR 1054 (42S22): Unknown column in 'field list'
The query references a column that doesn’t exist in the table (or an unquoted string being read as a column).
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
GraphQL: Cannot query field "x" on type "Y"
The query asks for a field that doesn’t exist in the server’s schema (or isn’t available on that type).
PostgreSQL: FATAL: password authentication failed for user
PostgreSQL rejected the password for that role, or pg_hba.conf requires a different auth method.
django.db.utils.OperationalError: no such table: app_model
Django queried a table that hasn’t been created — migrations missing or not applied.
SQL Server: Invalid object name 'x'. (Msg 208)
The table/view doesn’t exist in the current database or schema.
MySQL ERROR 1044 (42000): Access denied for user to database
The login succeeded, but the user has no privileges on the database you’re using.
MySQL ERROR 1064 (42000): You have an error in your SQL syntax
MySQL couldn’t parse the query. The text after “near” shows where parsing failed.
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.
Column reference is ambiguous / Column 'id' in field list is ambiguous (MySQL 1052)
A column name exists in more than one joined table, so the database doesn’t know which one you mean.
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: syntax error at or near "x"
PostgreSQL couldn’t parse the SQL; the token shown is where parsing failed.
Room cannot verify the data integrity. Looks like you've changed schema but forgot to update the version number
The Room entity definitions changed, but the database version wasn’t increased or no migration was provided.
MySQL ERROR 1406: Data too long for column
The value is longer than the column allows (e.g. 300 characters into VARCHAR(255)), and strict mode rejects it instead of truncat…
MySQL ERROR 1005 (HY000): Can't create table (errno: 150 "Foreign key constraint is incorrectly formed")
A foreign key definition is invalid — the referenced column’s type, index or charset doesn’t match.
MySQL ERROR 1007 (HY000): Can't create database 'x'; database exists
CREATE DATABASE ran for a database that already exists.
MySQL ERROR 1008 (HY000): Can't drop database 'x'; database doesn't exist
DROP DATABASE targeted a database that isn’t there.
MySQL ERROR 1067 (42000): Invalid default value for 'created_at'
A column’s DEFAULT isn’t allowed in the current SQL mode — classically '0000-00-00 00:00:00' with NO_ZERO_DATE.
MySQL ERROR 1075 (42000): Incorrect table definition; there can be only one auto column and it must be defined as a key
An AUTO_INCREMENT column isn’t indexed (or there are two auto-increment columns).
pg_dump: error: aborting because of server version mismatch
Your pg_dump client is older than the server you’re dumping.
pg_restore: error: input file appears to be a text format dump. Please use psql.
A plain .sql dump was given to pg_restore, which only reads custom/directory/tar formats.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException