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
I'd also be interested in a use case for a single config option to disable reverse engineering any indexes without needing to list them individually. If we're reverse engineering an EF Core model that will never use code first, modeling the indexes doesn't really provide value and can cause a lot of noisy git changes if we reverse engineer against an Azure db with auto-managed indexing.
In #2520, support was added for an explicit list of indexes to exclude when reverse engineering.
e.g.,
I'd also be interested in a use case for a single config option to disable reverse engineering any indexes without needing to list them individually. If we're reverse engineering an EF Core model that will never use code first, modeling the indexes doesn't really provide value and can cause a lot of noisy git changes if we reverse engineer against an Azure db with auto-managed indexing.
That might look something like this:
I'm personally interested in attempting a PR to add support for this, but it wouldn't be for at least a month, and I'm not able to commit to it.
The text was updated successfully, but these errors were encountered: