SqlServerMigrationGenerator.FindDefaultConstraint uses the new column name to drop constraints of the old column

[Arnagos]

SqlServerMigrationGenerator.FindDefaultConstraint uses the new column name to drop constraints of the old column. This prevents the application form finding the existing default constraint when both the default value and the name of the column have changed at the same time.

Old column:

New column:

Result: Existing default value not found; new one gets created anyway -> System.Data.SqlClient.SqlException (0x80131904): Column already has a DEFAULT bound to it.

[martinjw]

Fixed in https://github.com/martinjw/dbschemareader/releases/tag/2.8.2.1 I hope
Will push to nuget later

[martinjw]

Now released to nuget