Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow excluding all indexes when reverse engineering #2850

Closed
collinbarrett opened this issue Feb 13, 2025 · 1 comment
Closed

Allow excluding all indexes when reverse engineering #2850

collinbarrett opened this issue Feb 13, 2025 · 1 comment
Assignees
Labels

Comments

@collinbarrett
Copy link

In #2520, support was added for an explicit list of indexes to exclude when reverse engineering.

e.g.,

{
   "Name": "[dbo].[my_table]",
   "ObjectType": 0,
   "ExcludedIndexes": [
       "IX_name_of_index_to_exclude_1",
       "IX_name_of_index_to_exclude_2",
   ]
}

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:

{
   "Name": "[dbo].[my_table]",
   "ObjectType": 0,
   "ExcludeAllIndexes": true
}

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.

@ErikEJ
Copy link
Owner

ErikEJ commented Feb 19, 2025

@collinbarrett Related issue, possibly a T4 template is a better solution? dotnet/efcore#10890

@ErikEJ ErikEJ closed this as not planned Won't fix, can't repro, duplicate, stale Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants