Your argument is clear and persuasive. I agree: the tool should AutoCommit => 1 and let the user turn that off if they have a reason for doing so.
For the record, the reason the tool does not do this already is because it was originally designed to simply blast a server with queries in order to load CPU cores and MySQL--that's it, nothing else, and no other considerations. So the current code is rather simplistic and does not include a lot of thought about general use-cases.
Your argument is clear and persuasive. I agree: the tool should AutoCommit => 1 and let the user turn that off if they have a reason for doing so.
For the record, the reason the tool does not do this already is because it was originally designed to simply blast a server with queries in order to load CPU cores and MySQL--that's it, nothing else, and no other considerations. So the current code is rather simplistic and does not include a lot of thought about general use-cases.