镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Breaking change note: a filtered index no longer replaces the index on a foreign key - #5525

Draft
ajcvickers wants to merge 1 commit into
dotnet:mainfrom
ajcvickers:breaking-change-filtered-index-fk-index
Draft

ajcvickers wants to merge 1 commit into
dotnet:mainfrom
ajcvickers:breaking-change-filtered-index-fk-index

Conversation

@ajcvickers

Copy link
Copy Markdown
Contributor

Adds a breaking change note to the EF Core 12 breaking changes page for dotnet/efcore#39652 (fixes dotnet/efcore#24237).

An index with an explicit filter no longer counts as covering a foreign key, so the foreign key's own index is created, and the next migration contains a CreateIndex for it. Convention-set filters (such as SQL Server's filter on unique indexes over nullable columns) are ignored and behave as before.

Draft until dotnet/efcore#39652 merges. Like the other open breaking change PRs, this adds ef-core-12.0/breaking-changes.md, so whichever merges second needs a trivial merge of the page.

🤖 Generated with Claude Code

…gn key index

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EF Core migration drops existing index on a column when a composite filtered index on that column is added

1 participant