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
See issue #14518. In this case, the property should be treated as store-generated by the update pipeline because:
It is configured to have a generated value
It has no associated value generator
This makes sense when the database already exists, but if the database is being created by migrations then we don't know what default constraint makes sense. Options discussed were:
Warn in Migrations (may need us to build a mechanism to do so)
Warn in model validation (warning will be shown even when database exists and is fine)
Set a sensible default constraint by convention (for example, newsequentialid() for GUIDs on SQL Server; less clear what makes sense for other types and other providers.)
The text was updated successfully, but these errors were encountered:
See issue #14518. In this case, the property should be treated as store-generated by the update pipeline because:
This makes sense when the database already exists, but if the database is being created by migrations then we don't know what default constraint makes sense. Options discussed were:
newsequentialid()
for GUIDs on SQL Server; less clear what makes sense for other types and other providers.)The text was updated successfully, but these errors were encountered: