ModelBuilder: API for removing indexes and foreign keys

[rowanmiller]

Split off from #7530

Currently there is no way to remove an index that was introduced by convention. You have to use internal APIs to do it.

[divega]

Possibly a generalization of #2725 could help this scenario, i.e. an annotation that once added to an element in metadata, instructs migrations not to create the corresponding database object for it.

[collinbarrett]

Ran into a requirement for this and finally stumbled upon this Issue. The workaround suggested by @AndriySvyryd here doesn't seem to work for me. Internal APIs may have changed.

Let me know if I can assist at all with this feature.

[AndriySvyryd]

@collinbarrett The current workaround is to disable conventions by calling

((Model)modelBuilder.Model).ConventionDispatcher.StartBatch();

But since this is also Internal code and will be broken in the future

[collinbarrett]

Ah, ok, thanks, @AndriySvyryd . Hmm, yeah, I probably don't want to disable conventions globally at this point. Will probably just manually remove from migrations for now. Thanks!

[AndriySvyryd]

The conventions will only be disabled after that call is made, so if the only thing that follows is removing indexes then nothing else would be affected, see #10855 (comment)

[ajcvickers]

Note: see workarounds on #6239.

[Shane32]

I'm having the same issue; I need a table without an index on a foreign key, and the above solutions are not officially supported, and the workaround listed in #6239 does not work. At the moment, I am manually modifying the migration to prevent the index from being created.

[schuettecarsten]

I have created an implementation of IModelFinalizingConvention and use this to remove all indexes from the model when the model builder finalizes it. This is a bit tricky, but works like a charm.

[rofenix2]

still no solution to this day?.