Description\n-----------\n\nThe IGNORE option tells the server to ignore some common errors.\n\nIGNORE can be used with the following statements:\n\n DELETE\n INSERT (see also INSERT IGNORE)\n LOAD DATA INFILE\n UPDATE\n ALTER TABLE\n CREATE TABLE ... SELECT\n INSERT ... SELECT\n\nThe logic used:\n\n Variables out of ranges are replaced with the maximum/minimum value.\n SQL_MODEs STRICT_TRANS_TABLES, STRICT_ALL_TABLES, NO_ZERO_IN_DATE, NO_ZERO_DATE are ignored.\n Inserting NULL in a NOT NULL field will insert 0 ( in a numerical field), 0000-00-00 ( in a date field) or an empty string ( in a character field).\n* Rows that cause a duplicate key error or break a foreign key constraint are not inserted, updated, or deleted.\n\nThe following errors are ignored:\n\n| Error number | Symbolic error name                              | Description                                                           |\n| ------------ | ------------------------------------------------ | --------------------------------------------------------------------- |\n| 1022         | ER_DUP_KEY                                     | Can't write; duplicate key in table '%s'                              |\n| 1048         | ER_BAD_NULL_ERROR                             | Column '%s' cannot be null                                            |\n| 1062         | ER_DUP_ENTRY                                   | Duplicate entry '%s' for key %d                                       |\n| 1242         | ER_SUBQUERY_NO_1_ROW                         | Subquery returns more than 1 row                                      |\n| 1264         | ER_WARN_DATA_OUT_OF_RANGE                   | Out of range value for column '%s' at row %ld                         |\n| 1265         | WARN_DATA_TRUNCATED                            | Data truncated for column '%s' at row %ld                             |\n| 1292         | ER_TRUNCATED_WRONG_VALUE                      | Truncated incorrect %s value: '%s'                                    |\n| 1366         | ER_TRUNCATED_WRONG_VALUE_FOR_FIELD          | Incorrect integer value                                               |\n| 1369         | ER_VIEW_CHECK_FAILED                          | CHECK OPTION failed '%s.%s'                                           |\n| 1451         | ER_ROW_IS_REFERENCED_2                       | Cannot delete or update a parent row                                  |\n| 1452         | ER_NO_REFERENCED_ROW_2                       | Cannot add or update a child row: a foreign key constraint fails (%s) |\n| 1526         | ER_NO_PARTITION_FOR_GIVEN_VALUE             | Table has no partition for value %s                                   |\n| 1586         | ER_DUP_ENTRY_WITH_KEY_NAME                  | Duplicate entry '%s' for key '%s'                                     |\n| 1591         | ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT     | Table has no partition for some existing values                       |\n| 1748         | ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET | Found a row not matching the given partition set                      |\n\nIgnored errors normally generate a warning.\n\nA property of the IGNORE clause consists in causing transactional engines and non-transactional engines (like InnoDB and Aria) to behave the same way. For example, normally a multi-row insert which tries to violate a UNIQUE contraint is completely rolled back on InnoDB, but might be partially executed on Aria. With the IGNORE clause, the statement will be partially executed in both engines.\n\nDuplicate key errors also generate warnings. The OLD_MODE server variable can be used to prevent this.\n\nURL: https://mariadb.com/docs/server/reference/sql-statements/data-manipulation/inserting-loading-data/ignore