Devart Forums

When modifying triggers and save when there is error, the old trigger is deleted but the new trigger cannot save.

After corrected the error, the new trigger still cannot save because the IDE report "trigger does not exist"

I did not encounter this problem before but I had not used that for quite some months so I don't know which version introduce this issue.

FYI, I am using the latest version (4.50.306) of the Professional Edition.

This is a known issue. We will fix it in the upcoming product versions.

Viktor wrote:This is a known issue. We will fix it in the upcoming product versions.

It is a pity that it is not fixed in the latest version upgrade

Again, this issue is not fixed in the version 4.50.313

The fix was not included into previous builds. All fixes included in each build are listed in the History file. Your fix request is enqueued.
We will notify you as soon as the next build with the fix of this issue is available for download.

Thanks for your reply.

I see that you do not need to use your own tools to do some real database management so you do not feel the inconvenient. It is reported 2 months ago and you said it is a known issue.

When Editing Triggers, a single minor mistake will make your tool to delete the trigger and cannot save again. And the "trigger do not exist" is clearly because your tools want to delete the now non-existing trigger. OK, I copied, closed that page and create the trigger again and the trigger cannot save because your cache tell that that trigger already exist .... I had to refresh the table, and create the trigger the 3rd time to save back that trigger.

The currently version add a try to restore the just deleted trigger when the save is not successful which of cause did not help anything.

Just remove the delete behaviour if last save is not success, or do the create trigger even when mysql report the trigger do not exist, can solve the problem. It is hard to believe such an excellent tools cannot get this simple issue fix in 2 months.

Sorry for inconvenience. We've fixed this problem at last.

Please download the new version (4.50.314) of dbForge Studio for MySQL or use Check Updates functionality to get information about new builds.

Please feel free to email us directly with any more feedback, suggestions or questions.

Thank you very much for your fast fix and response.

Sorry for the attitude of my last post in the thread. I was just annoyed by the tone of Viktor in his last post.

Actually I am very satisfied with your products and support, including dbForge for MySQL as well as our other purchase of MyDAC and Secure Bridge. The are all with very high standard and I always got reported problem solved or even feature request added in short period.

Thanks again for your great products and support.