Optimize remove query for multiple rows

Hello,

As it seems to me, HeidiSQL currently executes each remove query after the other (when removing multiple rows), meaning, it waits for one to execute, to execute the next. That seems a bit inefficient.

In JavaScript, there is a method called Promise.all() which allows for an array of promises to be passed as a parameter. The method will resolve after all promises inside the passed array are resolved. Maybe there is something similar for whatever language HeidiSQL uses.

But idk, maybe there is a reason for the current implementation.

Kind regards, Max