Comments
Sort by recent activity
I have tried the script before I posted a question here. The column's order is not saved in the table, i.e. the new columns are added at the end of the table.
To be more specific, the case is as follows: The table has one column which was renamed (which should be interpreted to a remove and add operations while its "index" should be preserved). There's also a new column which was added at the middle and a few that were added at the end. None of these columns appear in the order they should in the modified table (after executing the script on the database).
To conclude: the ForceColumnOrder has no affect on the comparison sync script. / comments
I have tried the script before I posted a question here. The column's order is not saved in the table, i.e. the new columns are added at the end of the table.
To be more specific, the case is as fo...