Critical bug in DBForge MySQL
Posted: Mon 07 Mar 2022 20:41
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.
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.