Repository navigation
Add EFCore.ComplexIndexes to EF Core extensions - #5495
Open
CaffeinatedCoder wants to merge 1 commit into
Open
CaffeinatedCoder wants to merge 1 commit into
CaffeinatedCoder wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Contributor
|
LGTM! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds EFCore.ComplexIndexes to the extensions list. I maintain it.
It generates migration SQL for indexes on the nested columns of complex properties, which EF Core 10 models but does not index. The core package is provider-agnostic; separate PostgreSQL and SQL Server packages add provider-specific options (PostgreSQL index methods, expression indexes, exclusion and temporal constraints; SQL Server clustered, covering and online indexes).
EF Core 11 indexes complex-type members natively (dotnet/efcore#31246), so the entry states EF Core 10, the line the packages target.
The entry follows the format of the existing ones: description ending in the supported EF Core versions, then repository and NuGet links, added at the end of the Extensions section.