Open abergmeier opened 3 years ago
For operations like adding a Column to the end or removing a Column, there is no need to recreate the table.
These changes can be incorporated by ALTER TABLE
statements.
The problem is, to make this transparent to the user, it would be necessary to implement CustomizeDiff
.
In turn CustomizeDiff
would have to analyze which operation will take place.
The operation can be determined in two ways:
Both seem bad choices because:
Also this still leaves the need to recreate for adding a Column not to the end. Since this seems like a very popular use-case, disregard the implementation for now.
Currently changing
composite
enforces a recreation of the table. Would be better to have a logic where the Table Columns are altered.