Schema comparison [7.4.201]

[matneves]

After update to 7.4.201, I've got the error: "An unbreakable cycle has been detected, which involves the following objects", just after the comparison ends.



I've managed to avoid this error by disabling the option "Disable dependency analysis", however by doing this, the comparison does not generates the sync script. What should I do to stop this error?

There's also a change on the trigger sync behavior. They were treated as a separated elements when doing the compare, now the trigger it's a part of the table's comparison. Is there a way to compare separating those elements?

[alexa]

After update to 7.4.201, I've got the error: "An unbreakable cycle has been detected, which involves the following objects", just after the comparison ends.

Could you please click the 'Report this problem' button in the dialog and send us the detailed report?

There's also a change on the trigger sync behavior. They were treated as a separated elements when doing the compare, now the trigger it's a part of the table's comparison. Is there a way to compare separating those elements?

We changed the functionality. Since DML triggers are sub-objects of the table, they are displayed as a part of the table.

There is no a possibility to compare triggers as separate objects anymore. However, you can use the following options:
- Ignore table DML triggers
- Ignore firing order for DML triggers
- Ignore triggers present only in Target

[matneves]

There is no a possibility to compare triggers as separate objects anymore.

This is sad, please consider to add an option for that. :(

Could you please click the 'Report this problem' button in the dialog and send us the detailed report?

I'll try to send the report and update you here. Thanks already for the response.

[matneves]

Alexa, I've got this error when trying to send the report:

[alexa]

Thank you for the reply.

Then, could you please perform the following:
1. Select 'Tools -> Options...' from the main menu. The 'Options' window opens.
2. Navigate to the 'Environment -> Output' branch.
3. Select the 'Write queries sent by the program to the SQL Log' and 'Log application errors' options.
4. Unselect the 'Delete application log after closing' option. Click 'OK'.
5. Reproduce the error and send us the *.log file with the latest date from the directory:

Code: Select all

%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\

[matneves]

Alexa, where should I send the .log file?

[alexa]

You can send it to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

[azadeh.adlamini]

What was the outcome of this issue? We have yet to upgrade to 7.4.xxx due to the unbreakable cycle error.

[alexa]

This issue will be fixed in the next product version that should be released this month.

[azadeh.adlamini]

Can you give me any information on how to currently resolve this issue? We are currently testing this release and have not upgraded to 7.4.xxx because of this error. Is there a workaround?

[alexa]

We've replied to you by e-mail on this.

[matneves]

Hey everyone! This issue has been fixed at 8.0.40, thanks a lot! 🚀

[alexa]

Thank you for updating us on this issue.