Error map
transaction SQLite: cannot start a transaction within a transaction
SQL · 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)
sqlite3.OperationalError: near "x": syntax error
SQLite couldn’t parse the statement; the token after “near” is where it stopped.
sqlite3.OperationalError: unable to open database file
SQLite couldn’t open or create the database file — wrong path or missing/unwritable directory.
Deadlock found when trying to get lock; try restarting transaction
Two transactions waited on each other’s locks; the database killed one so the other could continue.
Lock wait timeout exceeded; try restarting transaction (MySQL 1205)
A query waited too long for a row lock held by another transaction and gave up.
sqlite3.OperationalError: database is locked (SQLITE_BUSY)
Another connection holds a write lock on the SQLite file, and this one gave up waiting.
sqlite3.IntegrityError: UNIQUE constraint failed: users.email
An insert/update duplicated a value in a UNIQUE or PRIMARY KEY column in SQLite.
sqlite3.IntegrityError: FOREIGN KEY constraint failed
An insert/update/delete violated a foreign key in SQLite (with PRAGMA foreign_keys=ON).
sqlite3.DatabaseError: database disk image is malformed
The SQLite file is corrupted.
sqlite3.IntegrityError: NOT NULL constraint failed: table.column
A NULL went into a NOT NULL column in SQLite.
SQLite foreign keys not enforced: PRAGMA foreign_keys is OFF by default
Child rows can reference missing parents, and ON DELETE CASCADE doesn't run, because foreign key enforcement is disabled per conn…
Inconsistent results inside a transaction: non-repeatable and phantom reads (isolation level)
Two reads in the same transaction see different data because another transaction committed in between.
Changes disappear: transaction never committed (autocommit off, missing COMMIT)
Data inserted or updated "works" in your session but isn't there for others, or is gone after reconnecting.
Two steps away (36)
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.
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.
Column must appear in the GROUP BY clause / isn't in GROUP BY (MySQL 1055 only_full_group_by)
You selected a column that is neither grouped nor aggregated, so the result would be ambiguous.
FileNotFoundError: [Errno 2] No such file or directory: 'data.csv'
Python couldn’t find the file at that path — usually because relative paths resolve from the working directory, not the script.
sqlite3.OperationalError: no such column: x
SQLite can’t find the column — missing migration, typo, or a string written in double quotes.
sqlite3.OperationalError: attempt to write a readonly database
The process can’t write to the SQLite file or its directory.
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
MySQL ERROR 2006 (HY000): MySQL server has gone away
The connection to MySQL was closed — usually by a timeout or a packet larger than `max_allowed_packet`.
MySQL ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
MySQL detected a deadlock between two transactions and rolled one back.
MySQL ERROR 1040 (08004): Too many connections
MySQL reached `max_connections` and refuses new clients.
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.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
DDL or a NOWAIT lock couldn’t get the lock because another session holds it.
Terraform: Error: Error acquiring the state lock — ConditionalCheckFailedException / state blob is already locked
Another Terraform run holds the state lock, or a previous run crashed and left the lock behind.
SQL Server Msg 1205: Transaction was deadlocked on lock resources and has been chosen as the deadlock victim
Two sessions each hold locks the other needs, so SQL Server rolled one of them back.
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.
SQL Server: Violation of PRIMARY KEY constraint 'x'. Cannot insert duplicate key in object 'y'. (Msg 2627)
An insert duplicated a primary key or unique constraint value.
ORA-00001: unique constraint (SCHEMA.PK_X) violated
An insert/update duplicated a value in a unique or primary key constraint.
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.
SQL Server: The INSERT statement conflicted with the FOREIGN KEY constraint 'x'. (Msg 547)
The row references a parent that doesn’t exist (or a DELETE would orphan children).
SQLite: database or disk is full (SQLITE_FULL)
SQLite couldn't allocate more space: the disk, quota or a configured size limit is full.
error: object file .git/objects/x is empty / fatal: loose object is corrupt
The local Git object database is corrupted — usually after a crash, disk full or sync tool interference.
MySQL ERROR 126 (HY000): Incorrect key file for table; try to repair it
MySQL can’t use a table’s index file — usually a full tmp disk during a query, or MyISAM corruption.
ORA-00600: internal error code, arguments: [...]
Oracle hit an unexpected internal condition (a bug, corruption or hardware/OS problem).
ERROR: null value in column "x" of relation "y" violates not-null constraint
An INSERT/UPDATE put NULL into a NOT NULL column.
ORA-01400: cannot insert NULL into ("SCHEMA"."TABLE"."COLUMN")
A NULL was inserted into a NOT NULL column.
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.
Foreign key violation caused by insert order or circular references
Rows must be inserted parent-first, and two tables that reference each other need deferred constraints or nullable columns.
SQL Server Msg 3726: Could not drop object because it is referenced by a FOREIGN KEY constraint
You tried to drop a table that other tables still reference.
ORA-02291: integrity constraint (SCHEMA.FK_NAME) violated - parent key not found
You inserted/updated a child row whose foreign key value doesn't exist in the parent table.
java.util.ConcurrentModificationException
A collection was modified while being iterated (even in a single thread).
java.lang.InterruptedException (sleep interrupted)
A blocked thread (sleep, wait, join, queue take) was interrupted by another thread.
java.util.concurrent.TimeoutException
A Future.get(timeout) or async operation didn’t complete in the allowed time.
FATAL: terminating connection due to idle-in-transaction timeout
A session opened a transaction and sat idle longer than idle_in_transaction_session_timeout.
Query returns far too many rows: accidental Cartesian product (missing JOIN condition)
Two tables were joined without a condition, so every row of one pairs with every row of the other.
CASE expression returns mixed types: conversion failed / types cannot be matched
The branches of a CASE expression produce incompatible data types (text and number, date and string).
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError