Schema Sync – Ignore Field Order?

[ken]

I am trying to do a Schema Sync, and I am getting uesless results, in that many fields are showing up as different, but the SQL DDE for them contains AFTER. So it looks like maybe the field is being defined IDENTICALLY, except that the field order in the table is different. I consider these two fields to be equivalent in this case, as it doesn't matter to me in the slightest if the field order is different (of course).

Anyway, there should be an option to ignore field order in Schema Sync.

Is there?

Can we get it onto the list if not?

I am sorry to have to be looking at other products, but it looks like EMS's DB Comparer takes a more intelligent approach, making it easy to exclude what looks to be every detail of tables and fields from consideration. I attached a comparison result where I told the system that I don't care about collation or auto increment values for tables, nor do I care about field order. Note that the two tables shown are therefore considered idendical, which, for my purposes, they are- correct answer.

Any response?

Thanks,

K[attachment=1575:more-flexible-comparison-result.jpg]

[ashwin]

Hi,

We will discuss with the team and update here. Thanks for your suggestion.

[peterlaursen]

One reason the columns' order is synced is that Schema Sync should 'prepare tables for Data Sync”. For Data Sync identical columns order is mandatory as the algorithm is checksum-based. Checksum on a+b is not the same as on b+a. So we will not discard columns' order in Schema Sync. What we can consider however is an option for user to “ignore columns' order differences”.

We are in the process of finalizing the next (9.1) beta release. This one is feature frozen now. After releasing it we will return to this discussion. I cannot promise anything currently (neither IF nor WHEN we will provide this option).

[Author]

Posts