UPDATE ... ON DUPLICATE KEY

SQL defines an mechanism to handle inserts if a key is duplicate on insert.

In my opinon it is missing to do the same in case of updates. If you define unique keys, it could happen you have a manipulation which results in a duplicate key.
There is no (good) way to handle this case. Using ignore would ignore all errors not just duplicate keys (constraints, data to long, ...)