Error 1092 displays the summary line “Records: X Duplicates: Y Warnings: Z” after a data-loading or multi-row INSERT operation. It is informational but highlights duplicates and warnings that may need attention.
MySQL Error 1092 (ER_INSERT_INFO) is an informational message showing how many rows were processed, duplicated, or warned during LOAD DATA or multi-row INSERT statements. Investigate duplicates, review warnings, and adjust INSERT or table constraints to keep data integrity.
Records: %ld Duplicates: %ld Warnings: %ld
MySQL prints “Records: X Duplicates: Y Warnings: Z” when it finishes a LOAD DATA, INSERT … SELECT, or bulk INSERT statement. The server assigns code 1092 and condition ER_INSERT_INFO to this status line.
This is not a fatal error. It is a notification that some or all inserted rows met duplicate keys or generated warnings.
Ignoring it can leave unexpected data gaps or silent truncations.
The summary is returned to the client after the statement completes. Command-line tools echo the text, APIs expose it as info(), and editors like Galaxy show it in the result pane.
If Y or Z is greater than zero, data did not load exactly as intended. Investigating saves time later when queries show missing or inconsistent rows.
.
INSERT or LOAD DATA tried to insert rows that violate UNIQUE or PRIMARY KEY constraints. MySQL counted them in the Duplicates column.
Column length limits or strict mode conversions triggered warnings. These appear in the Warnings column and may silently modify data.
Missing values for NOT NULL columns caused warnings.
The row may insert with implicit defaults, hiding a data quality issue.
Storage engines such as InnoDB may skip or modify rows when foreign-key checks fail and foreign_key_checks is disabled, raising warnings.
.
No rows were rejected outright, but duplicates or warnings can hide data issues. Always review them.
The message is informational. Suppress it in client code by ignoring info() or by filtering stdout.
Check UNIQUE constraints and source data. Missing primary keys or repeated rows will inflate the count.
Yes. Galaxy surfaces MySQL warnings after each run and lets you annotate or fix the offending query before endorsing it.
.avif)
.avif){kind=logo}
