Error map

DECIMAL Money/decimal values rounded wrongly: FLOAT precision and DECIMAL scale mistakes

SQL · layer 5, Data

Open the full error page →

Centre: this error. First ring: errors it is linked with (9). 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.

DECIMAL — Money/decimal values rounded wrongly: FLOAT precision and DECIMAL scale mistakes (SQL)DECIMAL8115 — SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115) (SQL)811522003 — ERROR: numeric field overflow — A field with precision 5, scale 2 must round to an absolute value less than 10^3 (PostgreSQL)22003timezone — Timestamps off by hours: timezone, UTC and DST conversion mistakes (SQL)timezone= NULL — WHERE col = NULL returns no rows (use IS NULL) (SQL)= NULLcartesian — Query returns far too many rows: accidental Cartesian product (missing JOIN condition) (SQL)cartesianCASE — CASE expression returns mixed types: conversion failed / types cannot be matched (SQL)CASEinteger division — 5 / 2 = 2: integer division silently truncates the result (SQL)integer divisiondate format — Dates mixed up: dd/mm/yyyy vs mm/dd/yyyy, ISO 8601 recommended (SQL)date formatCOUNT — COUNT(column) ignores NULLs: counts differ from COUNT(*) (SQL)COUNT18456 — SQL Server: Login failed for user 'x'. (Error 18456) (SQL)18456208 — SQL Server: Invalid object name 'x'. (Msg 208) (SQL)208207 — SQL Server: Invalid column name 'x'. (Msg 207) (SQL)2071264 — MySQL ERROR 1264 (22003): Out of range value for column 'x' at row 1 (MySQL)126422P02 — ERROR: invalid input syntax for type integer: "abc" (PostgreSQL)22P0222P02 uuid — ERROR: invalid input syntax for type uuid: "x" (PostgreSQL)22P02 uuid1292 — MySQL ERROR 1292 (22007): Incorrect datetime value: 'x' for column 'y' (MySQL)129222008 — ERROR: date/time field value out of range: "31/12/2024" — HINT: Perhaps you need a different "datestyle" setting. (PostgreSQL)22008NOT IN — NOT IN (subquery) returns no rows because the subquery contains NULL (SQL)NOT INLEFT JOIN — LEFT JOIN returns fewer rows: a WHERE filter on the right table turns it into an INNER JOIN (SQL)LEFT JOIN515 — SQL Server Msg 515: Cannot insert the value NULL into column 'X', table 'Y'; column does not allow nulls (SQL)51557014 — ERROR: canceling statement due to statement timeout (PostgreSQL)57014out of shared memory — ERROR: out of shared memory — HINT: You might need to increase max_locks_per_transaction. (PostgreSQL)out of shared memoryN+1 queries — Performance: N+1 query problem (one query per row in a loop) (SQL)N+1 queriesAttributeError — AttributeError: 'X' object has no attribute 'y' (Python)AttributeErrorClassCastException — java.lang.ClassCastException: class A cannot be cast to class B (Java)ClassCastExceptionERR_INVALID_ARG_TYPE — TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined (Node.js)ERR_INVALID_ARG_TYPEDivision by zero — SQL Error: division by zero / Divide by zero error encountered (SQL)Division by zeroTS7016 — TS7016: Could not find a declaration file for module 'x'. 'x.js' implicitly has an 'any' type. (Node.js)TS7016TS2304 — TS2304: Cannot find name 'x'. (Node.js)TS2304DateTimeParseException — java.time.format.DateTimeParseException: Text '31/12/2024' could not be parsed at index 2 (Java)DateTimeParseExcept…Unparseable date — java.text.ParseException: Unparseable date: "x" (Java)Unparseable dateSetting locale failed — perl: warning: Setting locale failed / bash: warning: setlocale: LC_ALL: cannot change locale (Linux)Setting locale fail…aggregate in WHERE — ERROR: aggregate functions are not allowed in WHERE (use HAVING) / MySQL 1111 Invalid use of group function (SQL)aggregate in WHEREORDER BY with DISTINCT — ORDER BY items must appear in the select list if SELECT DISTINCT is specified (SQL)ORDER BY with DISTI…double quotes — "column" not found: double quotes mean identifiers, single quotes mean strings (SQL)double quotes

Directly related (9)

8115SQL

SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115)

A value or calculation exceeds the target data type’s range.

22003PostgreSQL

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.

timezoneSQL

Timestamps off by hours: timezone, UTC and DST conversion mistakes

Stored times appear shifted by 5 or 8 hours, or events shift around daylight saving changes.

= NULLSQL

WHERE col = NULL returns no rows (use IS NULL)

Comparing anything to NULL with = or never matches, because the result is UNKNOWN, not true.

cartesianSQL

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.

CASESQL

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).

integer divisionSQL

5 / 2 = 2: integer division silently truncates the result

Dividing two integers returns an integer in most databases, so decimals are dropped.

date formatSQL

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.

COUNTSQL

COUNT(column) ignores NULLs: counts differ from COUNT(*)

`COUNT(col)` counts only non-NULL values, while `COUNT(*)` counts rows, so totals don't match.

Two steps away (26)

18456SQL

SQL Server: Login failed for user 'x'. (Error 18456)

SQL Server rejected the login — wrong password, wrong authentication mode, or a disabled/missing login.

208SQL

SQL Server: Invalid object name 'x'. (Msg 208)

The table/view doesn’t exist in the current database or schema.

207SQL

SQL Server: Invalid column name 'x'. (Msg 207)

SQL Server can’t find the column — typo, missing migration, or a string in double quotes with QUOTED_IDENTIFIER ON.

1264MySQL

MySQL ERROR 1264 (22003): Out of range value for column 'x' at row 1

A number is too large (or negative for UNSIGNED) for the column type.

22P02PostgreSQL

ERROR: invalid input syntax for type integer: "abc"

A string couldn’t be converted to the column’s type (integer, numeric, boolean, date…).

22P02 uuidPostgreSQL

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.

1292MySQL

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.

22008PostgreSQL

ERROR: date/time field value out of range: "31/12/2024" — HINT: Perhaps you need a different "datestyle" setting.

PostgreSQL parsed a date in the wrong order (DMY vs MDY) or got an impossible value.

NOT INSQL

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.

LEFT JOINSQL

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.

515SQL

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.

57014PostgreSQL

ERROR: canceling statement due to statement timeout

A query ran longer than statement_timeout and PostgreSQL cancelled it.

out of shared memoryPostgreSQL

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.

N+1 queriesSQL

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.

AttributeErrorPython

AttributeError: 'X' object has no attribute 'y'

You accessed an attribute or method that doesn’t exist on that object type.

ClassCastExceptionJava

java.lang.ClassCastException: class A cannot be cast to class B

An object was cast to a type it isn’t.

ERR_INVALID_ARG_TYPENode.js

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.

Division by zeroSQL

SQL Error: division by zero / Divide by zero error encountered

An expression divided by a value that was 0 for at least one row.

TS7016Node.js

TS7016: Could not find a declaration file for module 'x'. 'x.js' implicitly has an 'any' type.

The JavaScript package has no TypeScript types bundled and no @types package installed.

TS2304Node.js

TS2304: Cannot find name 'x'.

TypeScript doesn’t know an identifier — a missing import, missing type definitions (e.g. for Node or Jest globals), or a typo.

DateTimeParseExceptionJava

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.

Unparseable dateJava

java.text.ParseException: Unparseable date: "x"

SimpleDateFormat couldn’t parse the string with its pattern.

Setting locale failedLinux

perl: warning: Setting locale failed / bash: warning: setlocale: LC_ALL: cannot change locale

Your session asks for a locale (often forwarded by SSH from your Mac/PC) that isn’t generated on the server.

aggregate in WHERESQL

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 with DISTINCTSQL

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.

double quotesSQL

"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.