Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute
5.0.1.5
See the version list below for details.
dotnet add package Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute --version 5.0.1.5
NuGet\Install-Package Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute -Version 5.0.1.5
<PackageReference Include="Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute" Version="5.0.1.5" />
<PackageVersion Include="Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute" Version="5.0.1.5" />
<PackageReference Include="Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute" />
paket add Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute --version 5.0.1.5
#r "nuget: Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute, 5.0.1.5"
#:package Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute@5.0.1.5
#addin nuget:?package=Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute&version=5.0.1.5
#tool nuget:?package=Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute&version=5.0.1.5
IndexColumnAttribute for Entity Framework Core

What's this?
This library brings the [Index] attribute of EF 6 back to EF Core, as the [IndexColumn] attribute. It also includes extension methods that build the indexes in your model from these attributes.
The automated tests check that it works on SQL Server, PostgreSQL, and SQLite.
Attention
Since ver.5.0, EF Core has its own official [Index] attribute.
However, I will keep maintaining and improving these libraries, because they still have some advantages.
- You can create indexes with data annotations even on an older version of EF Core.
- You can create indexes with included columns on SQL Server.
- You can create a clustered index. This means you can also create a non-clustered primary key.
How to use?
- Add the
Toolbelt.EntityFrameworkCore.IndexAttributepackage to your project.
> dotnet add package Toolbelt.EntityFrameworkCore.IndexAttribute
Supported Versions
| EF Core version | Package version |
|---|---|
| v.3.1, 5, 6, 7, ...11 | v.5.0.1 or later (Recommended), v.5.0, v.3.2, v.3.1 |
| v.3.0 | v.5.0.1 or later (Recommended), v.5.0, v.3.2, v.3.1, v.3.0 |
| v.2.0, 2.1, 2.2 | v.2.0.x |
If you want to use the IsClustered=true or Includes features on SQL Server, add the Toolbelt.EntityFrameworkCore.IndexAttribute.SqlServer package to your project instead.
> dotnet add package Toolbelt.EntityFrameworkCore.IndexAttribute.SqlServer
- Annotate your model with the
[IndexColumn]attribute. It lives in theToolbelt.ComponentModel.DataAnnotations.Schema.V5namespace.
Notice - The attribute name is [IndexColumn], not [Index]. EF Core 5.0 and later already use the name [Index].
using Toolbelt.ComponentModel.DataAnnotations.Schema.V5;
public class Person
{
public int Id { get; set; }
[IndexColumn] // <- Here!
public string Name { get; set; }
}
- [Important] Override the
OnModelCreating()method of your DbContext class, and call theBuildIndexesFromAnnotations()extension method. It lives in theToolbelt.ComponentModel.DataAnnotationsnamespace.
using Microsoft.EntityFrameworkCore;
using Toolbelt.ComponentModel.DataAnnotations;
public class MyDbContext : DbContext
{
...
// Override "OnModelCreating", ...
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
base.OnModelCreating(modelBuilder);
// .. and invoke "BuildIndexesFromAnnotations"!
modelBuilder.BuildIndexesFromAnnotations();
}
}
If you use the IsClustered=true or Includes = new[]{"Foo", "Bar"} features on SQL Server, call the BuildIndexesFromAnnotationsForSqlServer() extension method instead of BuildIndexesFromAnnotations().
...
// Override "OnModelCreating", ...
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
base.OnModelCreating(modelBuilder);
// Invoke "BuildIndexesFromAnnotationsForSqlServer"
// instead of "BuildIndexesFromAnnotations".
modelBuilder.BuildIndexesFromAnnotationsForSqlServer();
}
That's all!
The BuildIndexesFromAnnotations() (or BuildIndexesFromAnnotationsForSqlServer()) extension method scans the DbContext with .NET reflection, finds the [IndexColumn] attributes, and builds the indexes in the model.
As a result, the database that EF Core creates has the indexes that you specified with the [IndexColumn] attributes.
Appendix A - Suppress "NotSupportedException"
You will get a "NotSupportedException" when you call BuildIndexesFromAnnotations() with a model that has an [IndexColumn] attribute whose "IsClustered" property is true, or whose "Includes" property is not empty.
If you still need to call BuildIndexesFromAnnotations() in this case (for example, to share the model between different database products), you can suppress the exception with options, like this.
...
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
base.OnModelCreating(modelBuilder);
// Suppress "NotSupportedException" for "IsClustered" and "Includes" features.
modelBuilder.BuildIndexesFromAnnotations(options => {
options.SuppressNotSupportedException.IsClustered = true;
options.SuppressNotSupportedException.Includes = true;
});
}
}
Appendix B - Notes on "IsClustered=true"
Suppose you simply annotate the model with "IsClustered=true", like this.
public class Employee {
public int Id { get; set; }
[IndexColumn(IsClustered = true)]
public string EmployeeCode { get; set; }
}
Then you will get a 'System.Data.SqlClient.SqlException' like this.
System.Data.SqlClient.SqlException :
Cannot create more than one clustered index on table '(table name)'.
Drop the existing clustered index '(index name)' before creating another.
In this case, annotate the primary key property with the [PrimaryKey(IsClustered = false)] attribute explicitly. This stops the primary key from becoming a clustered index automatically.
public class Employee {
[PrimaryKey(IsClustered = false)] // <- Add this line!
public int Id { get; set; }
[IndexColumn(IsClustered = true)]
public string EmployeeCode { get; set; }
}
Appendix C - If you want to use only "IndexAttribute" without any dependencies...
If you want to use only the "IndexColumnAttribute" class without any dependencies, use the Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute NuGet package.
Appendix D - Upgrade an existing project
For more details on this topic, see this link.
Appendix E - If you run into a compile error CS0104...
For more details on this topic, see this link.
For More Details...
This library uses the same syntax as the [Index] attribute of EF 6.x.
See the EF 6.x documents below for more details.
Limitations
The [IndexColumn] attribute with IsClustered=true works only on entity types that are not owned types.
Don't give a name to [PrimaryKey] on a base class property, such as [PrimaryKey("PK_Items")], when you use the table-per-type (TPT) or table-per-concrete-type (TPC) mapping. EF Core gives that one name to the primary key of every table in the hierarchy, so SQL Server and PostgreSQL fail to create the tables because of the duplicate name. Use [PrimaryKey] without a name instead. Then EF Core names each primary key after its own table.
Release Notes
- Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute
- Toolbelt.EntityFrameworkCore.IndexAttribute
- Toolbelt.EntityFrameworkCore.IndexAttribute.SqlServer
License
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
| .NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
| .NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
| .NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
| MonoAndroid | monoandroid was computed. |
| MonoMac | monomac was computed. |
| MonoTouch | monotouch was computed. |
| Tizen | tizen40 was computed. tizen60 was computed. |
| Xamarin.iOS | xamarinios was computed. |
| Xamarin.Mac | xamarinmac was computed. |
| Xamarin.TVOS | xamarintvos was computed. |
| Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- No dependencies.
NuGet packages (5)
Showing the top 5 NuGet packages that depend on Toolbelt.EntityFrameworkCore.IndexAttribute.Attribute:
| Package | Downloads |
|---|---|
|
Toolbelt.EntityFrameworkCore.IndexAttribute
The `[IndexColumn]` attribute that is the revival of `[Index]` attribute for EF Core. (with extension for model building.) This package also provides [PrimaryKey] attribute. |
|
|
BinaryBlox.SDK
Package Description |
|
|
Consist.OperationLog
Package Description |
|
|
ElevenFiftyNine.SDK
Package Description |
|
|
BinaryBlox.NetCore.Common
BinaryBlox: Common Library |
GitHub repositories
This package is not used by any popular GitHub repositories.
v.5.0.1.5
- No changes other than the version number