Closed davisnw closed 3 years ago
Thank you for a very detailed issue. Yes that looks like a bug and I will try to look at it sometime, but it won't be soon. Making EfSchemaCompare work for all options is a challenge!
I have split the EfSchemaCompare out into its own project and added a lots of features/fixes, especially around EF Core 5 new features.
I looked at checking alternative keys and its not easy, so I haven't implemented it. I do now list "alternative keys" as a limitation in the documentation.
Testing with EfCore.TestSupport 3.1.1 nuget package.
I don't see this listed in https://github.com/JonPSmith/EfCore.TestSupport/wiki/EfSchemaCompare-limitations,
It seems like it should be able to be treated similarly to a unique index, which is detected when missing.
Duplication: