Error map
= NULL WHERE col = NULL returns no rows (use IS NULL)
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (8). 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 (8)
SQL Server Msg 515: Cannot insert the value NULL into column 'X', table 'Y'; column does not allow nulls
An INSERT or UPDATE tried to put NULL into a NOT NULL column that has no default.
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.
LEFT JOIN returns fewer rows: a WHERE filter on the right table turns it into an INNER JOIN
A condition on the right-hand table in WHERE removes the NULL-extended rows that a LEFT JOIN was supposed to keep.
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).
Dates mixed up: dd/mm/yyyy vs mm/dd/yyyy, ISO 8601 recommended
A date string like 03/04/2026 is read as March 4th or April 3rd depending on locale, so rows get wrong dates or conversion errors.
COUNT(column) ignores NULLs: counts differ from COUNT(*)
`COUNT(col)` counts only non-NULL values, while `COUNT(*)` counts rows, so totals don't match.
NOT IN (subquery) returns no rows because the subquery contains NULL
If the list or subquery for NOT IN contains a single NULL, the whole condition is UNKNOWN and no rows come back.
Money/decimal values rounded wrongly: FLOAT precision and DECIMAL scale mistakes
Sums of FLOAT/REAL values drift (0.1 + 0.2 != 0.3), or a DECIMAL column rounds values you inserted.
Two steps away (23)
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.
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: canceling statement due to statement timeout
A query ran longer than statement_timeout and PostgreSQL cancelled it.
ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction.
A transaction took more locks than the lock table can hold — usually touching many tables/partitions at once.
Performance: N+1 query problem (one query per row in a loop)
Code runs one query to load a list, then one more query per item — hundreds of queries per page.
Duplicate rows and inflated SUM() after joining a one-to-many table
Joining a parent to a child multiplies parent rows, so totals and counts are too big.
SQL Server Msg 4104: The multi-part identifier could not be bound
A table alias or column reference used in the query isn't in scope.
SQL Server Msg 209: Ambiguous column name
A column exists in more than one table of the query and isn't qualified.
AttributeError: 'X' object has no attribute 'y'
You accessed an attribute or method that doesn’t exist on that object type.
java.lang.ClassCastException: class A cannot be cast to class B
An object was cast to a type it isn’t.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
A Node API got an argument of the wrong type — usually undefined because an env var or config value is missing.
java.time.format.DateTimeParseException: Text '31/12/2024' could not be parsed at index 2
A java.time parse call got text that doesn’t match the expected format.
java.text.ParseException: Unparseable date: "x"
SimpleDateFormat couldn’t parse the string with its pattern.
MySQL ERROR 1292 (22007): Incorrect datetime value: 'x' for column 'y'
A string couldn’t be converted to DATE/DATETIME — wrong format, empty string, or a zero date in strict mode.
ERROR: aggregate functions are not allowed in WHERE (use HAVING) / MySQL 1111 Invalid use of group function
An aggregate (SUM, COUNT, AVG) was used in WHERE, which filters rows before grouping.
ORDER BY items must appear in the select list if SELECT DISTINCT is specified
With DISTINCT, the database can only sort by columns that are part of the selected result.
"column" not found: double quotes mean identifiers, single quotes mean strings
In standard SQL double quotes quote identifiers, so "abc" is read as a column name, not a text value.
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.
ORA-01427: single-row subquery returns more than one row
A subquery used where one value is expected returned several rows.
ERROR: numeric field overflow — A field with precision 5, scale 2 must round to an absolute value less than 10^3
A number doesn’t fit the column’s numeric(precision, scale) or integer range.
SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115)
A value or calculation exceeds the target data type’s range.
5 / 2 = 2: integer division silently truncates the result
Dividing two integers returns an integer in most databases, so decimals are dropped.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError