Sometimes while performing update or delete SQL operations with WHERE condition containing many non-existent IDs the lock of all table rows occurred on MySQL type databases. The more detailed explanation of the following issue can be found in comments of ZBX-26436. While ZBX-26436 is minimizing the given problem only for the hosts, templates and their sub-entities (like items, triggers, LLD rules, etc.), it's necessary to minimize this for the rest of *.delete API methods. And that's what this ticket is for.