Version: 9.0.304 (Enterprise)
This error has been around since 2019. When you have a table you're 'working on' and rename the table (even with no FK constraints or external connected references), when you refactor, the system breaks down and doesn't allow you to save the table, requiring exit without saving. When you save and exit the .dbd, the table is gone from the diagram, and you must manually drag and drop the new (renamed) table from the table list to re-add it to the diagram.
In the below example, all I did was rename the table from system_log_error_notification to system_log_error_review and refactored.
dbForge MySQL 2020 Bug - Renaming Table and refactoring results in error
Re: dbForge MySQL 2020 Bug - Renaming Table and refactoring results in error
Unfortunately, we were not able to reproduce this issue.
Could you please describe it step by step and provide us the CREATE definition of the table?
A video or screenshots would be also of help.
You can send the reply straight to our support system at supportATdevartDOTcom.
Could you please describe it step by step and provide us the CREATE definition of the table?
A video or screenshots would be also of help.
You can send the reply straight to our support system at supportATdevartDOTcom.
Re: dbForge MySQL 2020 Bug - Renaming Table and refactoring results in error
I created a video showing how to reproduce this issue. I hope it helps!
https://1drv.ms/u/s!Au1rXgEghmrsh1ISHfi ... W?e=U4Ap5a
https://1drv.ms/u/s!Au1rXgEghmrsh1ISHfi ... W?e=U4Ap5a
Re: dbForge MySQL 2020 Bug - Renaming Table and refactoring results in error
Thank you for the reply.
We were able to reproduce it and will fix it in one of the next product builds.
We were able to reproduce it and will fix it in one of the next product builds.