> 3. Use a bouncer which can either disallow these changes or detect and revert them after the original client has disconnected. I'm not sure if this exists for

> 3. Use a bouncer which can either disallow these changes or detect and revert them after the original client has disconnected. I'm not sure if this exists for MySQL at least. I believe ProxySQL does exactly that: * https://proxysql.com/documentation/mysql-prepared-statements-pooling-and-caching/ https://proxysql.com/documentation/mysql-prepared-statements... * https://proxysql.com/documentation/multiplexing/ https://proxysql.com/documentation/multiplexing/