You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of foreign keys, the auto-generated constraint name may be overruled by invoking .HasConstraintName.
It seems like there currently is no .HasConstraintName for these enum related constraints. In my opinion, you need to add that, so these auto-generated names can also be overridden because otherwise these constraints will prevent usage of EF Core.
The text was updated successfully, but these errors were encountered:
I have several cases, where the auto-generated name for an enum constraint is too long, i.e. > 128 characters. It is this feature I talk about: https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-5.0/whatsnew#generation-of-check-constraints-for-enum-mappings
In case of foreign keys, the auto-generated constraint name may be overruled by invoking
.HasConstraintName
.It seems like there currently is no
.HasConstraintName
for these enum related constraints. In my opinion, you need to add that, so these auto-generated names can also be overridden because otherwise these constraints will prevent usage of EF Core.The text was updated successfully, but these errors were encountered: