Do you have any plans to add the mitigation for the workaround in the latest version of EF Core for tables with computed fields that use Functions()? https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-7.0/breaking-changes#sql-server-tables-with-triggers-or-certain-computed-columns-now-require-special-ef-core-configuration

We have several legacy databases which we are slowly migrating to micro-services and EF Core, but a reasonable number of these tables contain convenience fields that use computed fields which contain scalar functions. In the latest release of EF Core, saving a record to these tables fails.

There is a mitigation which we manually add to the entity configuration currently, until we can look at all the computed fields. But I was wondering if this is something we could include in this generator? i.e. for tables that contain a computer field, and only those tables, force the old-style saving. That way I wouldn't miss any. ;-)