dbForge MySQL 2020 Bug - Disabling Autocommit in [mysqld] destroys dbForge

[Requnix]

If you set autocommit = 0 in the [mysqld] of the .ini, dbForge completely falls apart.

This tells me the IDE is executing non-transactional statements.

This also forces those who use dbForge to use an auto-commit environment, which is not proper for a large-scale complex environment. Granted we can disable autocommit for each stored procedure, it we need to do it globally for the instance of the database.

This is bad. Red flag bad.

[Requnix]

To confirm, doing a simple SET autocommit = 0; in any stored procedure also guarantees the IDE will hang.

This is a huge problem guys - very bad! Guarantees the IDE will crash for anyone who wants to turn off autocommit!

[alexa]

We will investigate this issue.

[Requnix]

Awesome - thanks for the quick response. I want to ensure the full release is as solid as possible since I rely on the tool for pretty much everything I do in MySQL :)