| | fails (%s) | +---------------------+---------------------------------+--------------------+ | 1526 | ER_NO_PARTITION_FOR_GIVEN_VALUE | Table has no | | | | partition for | | | | value %s | +---------------------+---------------------------------+--------------------+ | 1586 | ER_DUP_ENTRY_WITH_KEY_NAME | Duplicate entry | | | | '%s' for key '%s' | +---------------------+---------------------------------+--------------------+ | 1591 | ER_NO_PARTITION_FOR_GIVEN_VALUE | Table has no | | | SILENT | partition for | | | | some existing | | | | values | +---------------------+---------------------------------+--------------------+ | 1748 | ER_ROW_DOES_NOT_MATCH_GIVEN_PAR | Found a row not | | | ITION_SET | matching the | | | | given partition | | | | set | +---------------------+---------------------------------+--------------------+ Ignored errors normally generate a warning. A 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. Duplicate key errors also generate warnings. The OLD_MODE server variable can be used to prevent this. URL: https://mariadb.com/kb/en/ignore/https://mariadb.com/kb/en/ignore/