Error map
GROUP_CONCAT GROUP_CONCAT / STRING_AGG result truncated or fails (group_concat_max_len, string length limit)
SQL · layer 5, Data
Centre: this error. First ring: errors it is linked with (7). 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 (7)
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…
Numbers sort wrongly (1, 10, 2): VARCHAR column sorted as text
A numeric-looking column stored as text sorts alphabetically, so "10" comes before "2".
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).
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.
SQL Server Msg 8114: Error converting data type varchar to numeric
A text value that isn't a valid number was converted to DECIMAL/NUMERIC.
Two steps away (21)
MySQL ERROR 1062 (23000): Duplicate entry for key
An INSERT/UPDATE would create a duplicate value in a PRIMARY or UNIQUE key.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
MySQL ERROR 1366: Incorrect string value: '\xF0\x9F\x98\x80' for column
The text contains characters (usually emoji) that the column’s character set can’t store — the column or connection is `utf8`/`ut…
ERROR: invalid input syntax for type integer: "abc"
A string couldn’t be converted to the column’s type (integer, numeric, boolean, date…).
5 / 2 = 2: integer division silently truncates the result
Dividing two integers returns an integer in most databases, so decimals are dropped.
Query slow because of an implicit type conversion or function on the column (index not used)
Comparing a column to a different type, or wrapping it in a function, stops the database using the index.
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.
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.
WHERE col = NULL returns no rows (use IS NULL)
Comparing anything to NULL with = or never matches, because the result is UNKNOWN, not true.
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.
SQL Server: Conversion failed when converting the varchar value 'x' to data type int. (Msg 245)
SQL Server tried to convert text to a number (often implicitly) and hit a non-numeric value.
SQL Server: Arithmetic overflow error converting expression to data type int. (Msg 8115)
A value or calculation exceeds the target data type’s range.
SQL Server Msg 242: The conversion of a varchar data type to a datetime data type resulted in an out-of-range value
A date string couldn't be converted because it's invalid or in the wrong format for the session language.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError