EF Core 10 named default constraints solve an annoying SQL Server maintenance problem: database-generated names such as DF__Jobs__Status__... are hard to predict in scripts and incident playbooks. The new convention gives every default a stable name. The catch is easy to miss: enabling it on an existing model makes the next migration change every default constraint in that model. That is exactly the kind of small configuration edit that deserves a migration gate. I want to know how many col...