DB Comparison/synchronization issue 3 - Build Order

[MarkBrock]

after synchronization the output DDL script didn't contain the objects in the correct build order as defined in the selected project configuration.

[.jp]

after synchronization the output DDL script didn't contain the objects in the correct build order as defined in the selected project configuration.

Please give the example.

[MarkBrock]

I have i.e. two views, we call it
- v_sum
- v_sum_01
v_sum_01 contains a select of a table and v_sum selects data by using v_sum_01, so v_sum depends on v_sum_01.

In the configuration profile of my project on tab "Build Order", I have definded to create first v_sum_01 and then v_sum.

When building the project the DDL script contains the views in the correct order, as defined in the configuration profile.

When synchronizing with DB and the views didn't exists on the target db the synchronization script first tries to create the v_sum and then the v_sum_01.
That will fail, because v_sum need v_sum_01 to exist.
This seems, that the objects in the synchronization script are ordered by normal ascii order, this will give the answer why it adds first v_sum and then v_sum_01. But this is not the order I defined in the configuration profile.

I have detected the same problem in Schema and Data Comparison. But this is a general problem. Normally we need a feature, which automatically detects the dependencies of all objects (this could replace the manual definition of the build order in the configuration profile) and always adds the objects in the sql scripts in the order of dependencies.
This could be used in project independence Schema and Data Comparison and also for project depending synchronization, deploying and building.

Maybe you can think about this feature. Should be a good idea!

[Duke]

We are currently investigating the problem. Fast of all correct Project->Database synchronization will be implemented in the release of version 4.0.

[thecodeslinger]

I encountered this issue with the command line version 6.2.280. When I generate the sql file using the GUI, the views are created in the correct order. When I generate the sql file using the command line, the views are created in alphabetical order instead of taking into account which views depend on other views.

Is there a fix for this?

Thanks.

[alexa]

We were able to reproduce this issue and will fix it in one of the next product builds. We will notify you once it's available for downloading.

In the meanwhile, you can generate a *.scomp schema comparison document with the GUI of dbForge and use the generated file in the command line interface.

[alexa]

We would like to let you know that we have released a new version 6.3 of dbForge Studio for MySQL where this issue is fixed http://www.devart.com/dbforge/mysql/stu ... nload.html

Thank you for your help in improving dbForge Studio for MySQL.