Critical bug in DBForge MySQL

[francis]

I've been a dbforge user for 7+ years. Using build 9.0.791

1) select [field2] from [table] WHERE field1=XYZ;
2) query failed a few times due to missing db permissions for the user.
3) eventually dbforge went white and I closed it.
4) It relaunched immediately.
5) re-run select [field2] from [table] WHERE field1=XYZ;
5.1) one row is returned.
6) change the value of field2 (to 0) from the dbforge UI and click on apply.
7) ALL rows in our main people table got updated with field2=0 (holy hell). The update occurred without the WHERE clause somehow.

This happened again on a different database a bit later. I'm still waiting for yesterday's backup to download as I type this so I can restore the data. I stopped using dbforge and went back to mysql workbench before my company goes bankrupt due to this.

This is completely insane. Let me know if you need app logs before I uninstall it permanently.

[Raudar]

Hi there,

Please note that we always had this behavior in such situations and at the moment we always display the warning, that a unique key is missing (please see the screenshot):

https://prnt.sc/x3qjFIHcYwIo

We even tried blocking editing in such cases however, due to users' feedback, restored it back.

Regards,
Devart Support

[francis]

Hi,

No I had a WHERE clause which was ignored somehow by the update.

It was a million row table and my select returned only one row.

It is too dangerous to use your software until this issue is found.