The migration script does not take into account after which field a new one is added

[garfildalex6]

There is this problem:
when a new field is added between other fields

the migration script does not take this into account, and adds a new field to the end of the table

[drebrez]

Hi @garfildalex6,

there is a toggle in the project options tab to ignore the order of the columns during the comparison.

Let me know if that solves your problem.

[garfildalex6]

Hi, @drebrez
Thank you for your answer!
Unfortunately, your advice didn't help.
Here are my settings:

Here's a comparison:

As you can see in the screenshot, the "show_message" field is located BEFORE the "include_action_cancel" field.

And here is the migration script that the application created:

As you can see in the screenshot, script simply inserts the "show_message" field at the end of the table, that is, it will be located AFTER the "include_action_cancel" field (and not before it as it should be).

[drebrez]

Hi @garfildalex6,

you should try to toggle the "Ignore source table column order" and compare again

[garfildalex6]

Hello, @drebrez
Unfortunately this setting did not help:

Comparison:

Migration script:

[drebrez]

Hi @garfildalex6,

you are right, the feature to have the migration script that add a column in the correct order is missing.

Adding the feature for the "ADD COLUMN" sounds easy, but I'm a bit concerned about the whole logic to update the tables that have the columns in the wrong order.

I'll think about it.