Entity Framework Code First Fluent Api:向列添加索引
我正在运行 EF 4.2 CF,并希望在 POCO 对象中的某些列上创建索引。
举个例子,假设我们有这个员工类别:
public class Employee
{
public int EmployeeID { get; set; }
public string EmployeeCode { get; set; }
public string FirstName { get; set; }
public string LastName { get; set; }
public DateTime HireDate { get; set; }
}
我们经常通过员工代码搜索员工,并且由于有很多员工,出于性能原因将其编入索引会很好。
我们可以用 Fluent api 来做到这一点吗?或者也许是数据注释?
我知道可以执行这样的 sql 命令:
context.Database.ExecuteSqlCommand("CREATE INDEX IX_NAME ON ...");
我非常希望避免这样的原始 SQL。
我知道这不存在,但正在寻找类似的东西:
class EmployeeConfiguration : EntityTypeConfiguration<Employee>
{
internal EmployeeConfiguration()
{
this.HasIndex(e => e.EmployeeCode)
.HasIndex(e => e.FirstName)
.HasIndex(e => e.LastName);
}
}
或者也许使用 System.ComponentModel.DataAnnotations , POCO 可能看起来像这样(我再次知道这不存在):
public class Employee
{
public int EmployeeID { get; set; }
[Indexed]
public string EmployeeCode { get; set; }
[Indexed]
public string FirstName { get; set; }
[Indexed]
public string LastName { get; set; }
public DateTime HireDate { get; set; }
}
任何人都有任何想法如何做到这一点,或者是否有任何计划实施一种方法来做到这一点,代码优先的方式?
更新: 正如 Robba 的回答中提到的,此功能在 EF 版本 6.1 中实现
I'm running EF 4.2 CF and want to create indexes on certain columns in my POCO objects.
As an example lets say we have this employee class:
public class Employee
{
public int EmployeeID { get; set; }
public string EmployeeCode { get; set; }
public string FirstName { get; set; }
public string LastName { get; set; }
public DateTime HireDate { get; set; }
}
We often do searches for employees by their EmployeeCode and since there are a lot of employees it would be nice to have that indexed for performance reasons.
Can we do this with fluent api somehow? or perhaps data annotations?
I know it is possible to execute sql commands something like this:
context.Database.ExecuteSqlCommand("CREATE INDEX IX_NAME ON ...");
I would very much like to avoid raw SQL like that.
i know this does not exist but looking for something along those lines:
class EmployeeConfiguration : EntityTypeConfiguration<Employee>
{
internal EmployeeConfiguration()
{
this.HasIndex(e => e.EmployeeCode)
.HasIndex(e => e.FirstName)
.HasIndex(e => e.LastName);
}
}
or maybe using System.ComponentModel.DataAnnotations
the POCO could look like this (again i know this does not exist):
public class Employee
{
public int EmployeeID { get; set; }
[Indexed]
public string EmployeeCode { get; set; }
[Indexed]
public string FirstName { get; set; }
[Indexed]
public string LastName { get; set; }
public DateTime HireDate { get; set; }
}
Anyone have any ideas on how to do this, or if there are any plans to implement a way to do this, the code first way?
UPDATE: As mentioned in the answer by Robba, this feature is implemented in EF version 6.1
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(15)
EF 4.3 中引入迁移后,您现在可以在修改或创建表时添加索引。以下是 的摘录来自 ADO.NET 团队博客的 EF 4.3 基于代码的迁移演练
这是添加索引的一种很好的强类型方法,这正是我第一次发布问题时所寻找的。
After Migrations was introduced in EF 4.3 you can now add indexes when modifying or creating a table. Here is an excerpt from the EF 4.3 Code-Based Migrations Walkthrough from the ADO.NET team blog
This is a nice strongly typed way to add the indexes, which was what i was looking for when i first posted the question.
您可以创建一个名为“indexed”的属性(如您所建议的),然后在自定义初始值设定项中选取该属性。
我创建了以下属性:
然后创建了一个自定义初始值设定项,它获取为我的上下文中的实体创建的表名称列表。我的所有实体都继承了两个基类,因此我执行了以下操作来获取表名称:
然后我找到了每个具有此属性的实体上的所有属性,然后执行 SQL 命令来生成每个属性上的索引。甜的!
我什至继续以相同的方式添加基于类的索引(可以有多个列)、唯一约束和默认约束。真正好的一点是,如果将这些属性放在继承的类上,则索引或约束将应用于继承它的所有类(表)。
顺便说一句,复数助手包含以下内容:
You could create an attribute called indexed (as you suggested), which is then picked up in a custom initializer.
I created the following attribute:
I then created a custom initializer which got a list of the table names created for the entities in my context. I have two base classes which all my entities inherit, so I did the following to get the table names:
I then found all the properties on each entity that have this attribute and then execute a SQL command to generate the index on each property. Sweet!
I even went on to add class based indexes (which could have multiple columns) , unique constraints and default constraints all in the same way. Whats also really nice is that if you put these attributes on an inherited class the index or constraint gets applied to all the classes (tables) that inherit it.
BTW the pluralizer helper contains the following:
为了构建 freeze 的响应,您可以自己将其手动编码到迁移中。
首先,转到程序包管理器控制台并使用
add-migration
创建一个新的迁移,然后为其命名。将出现空白迁移。牢记这一点:请注意,如果您使用字符串字段,则它的长度也需要限制为 450 个字符。
To build on frozen's response, you can hand code it into a migration yourself.
First, go to the Package Manager Console and create a new migration with
add-migration
, then give it a name. A blank migration will appear. Stick this in:Note that if you're using a string field it needs to be capped to a length of 450 chars as well.
我最近也对此进行了研究,但没有找到其他方法,因此我决定在播种数据库时创建索引:
I've also looked into this recently and found no other way, so I settled with creating indexes when seeding the database:
请注意,在 Entity Framework 6.1(当前处于测试版)中,将支持 IndexAttribute 来注释索引属性,这将自动在您的 Code First 迁移中生成(唯一的)索引。
Note that in Entity Framework 6.1 (currently in beta) will support the IndexAttribute to annotate the index properties which will automatically result in a (unique) index in your Code First Migrations.
对于使用 Entity Framework 6.1+ 的任何人,您可以使用 Fluent api 执行以下操作:
在 文档中了解更多信息。
For anyone using Entity Framework 6.1+, you can do the following with fluent api:
Read more in the documentation.
好吧,我在网上找到了一个解决方案,并对其进行了调整以满足我的需求,它是:
然后在 dbcontext 中重载 OnModelCreating
将索引属性应用于您的实体类型,使用此解决方案,您可以在同一索引中拥有多个字段,只需使用相同的名称和独特的。
Well i found a solution online and adapted it to fit my needs here it is:
Then overload OnModelCreating in your dbcontext
Apply the index attribute to your Entity type, with this solution you can have multiple fields in the same index just use the same name and unique.
扩展 Tsuushin 的上述答案以支持多列和唯一约束:
Extending Tsuushin's answer above to support multiple columns and unique constraints:
在 Petoj 上扩展,
我将 CreateIndexQueryTemplate 修改为
并从 OnModelCreating 中删除了以下内容
,并将以下内容添加到配置播种方法中,
这样每次更新数据库时都会运行索引属性。
expanding on Petoj
i modified the CreateIndexQueryTemplate to
and removed the following from OnModelCreating
and added the following to Configuration Seeding method
this way the index attributes are run every time you do a update-database.
如果您希望将此功能添加到 EF,那么您可以在这里投票 http://entityframework.codeplex.com/工作项/57
If you want this feature added to EF then you can vote for it here http://entityframework.codeplex.com/workitem/57
jwsadler 的数据注释扩展非常适合我们。我们使用注释来影响类或属性的处理,并使用 Fluent API 来进行全局更改。
我们的注释涵盖索引(唯一和非唯一)加上 getdate() 和 (1) 的默认值。代码示例展示了我们如何将其应用到我们的情况。我们所有的类都继承自一个基类。这个实现做了很多假设,因为我们有一个非常简单的模型。我们使用实体框架 6.0.1。许多评论已被纳入其中。
这是我们的背景:
jwsadler's extension of Data Annotations was a nice fit for us. We use Annotations to influence the treatment of a class or property and Fluent API for global changes.
Our annotations cover indexes (unique and not unique) plus default values of getdate() and (1). The code sample shows how we applied it to our situation. All of our classes inherit from one base class. This implementation makes a lot of assumptions because we have a pretty simple model. We're using Entity Framework 6.0.1. Lots of comments have been included.
Here's our context:
为了进一步构建所有这些出色的响应,我们添加了以下代码,以便能够从关联的元数据类型中获取 Index 属性。有关完整详细信息,请 请参阅我的博文,但总的来说,这里是详细信息。
元数据类型的使用方式如下:
在本示例中,元数据类型是嵌套类,但不一定如此,它可以是任何类型。属性匹配仅按名称完成,因此元数据类型只需具有相同名称的属性,并且应用于该属性的任何数据注释都应应用于关联的实体类。这在原始解决方案中不起作用,因为它不检查关联的元数据类型。我们探索了以下辅助方法:
To build further on all these great responses, we added the following code to enable the Index attribute to be picked up from an associated metadata type. For the full details please see my blog post, but in summary here are the details.
Metadata types are used like this:
In this example the metadata type is a nested class, but it doesn't have to be, it can be any type. Property matching is done by name only, so the metadata type just has to have a property of the same name, and any data annotations applied to that should then be applied to the associated entity class. This didn't work in the original solution because it doesn't check for the associated metadata type. We plumbed in the following helper method:
对于 EF7,您可以使用
hasIndex()
方法。我们也可以设置聚集索引和非聚集索引。
默认情况下主键将是聚集的。我们也可以改变这种行为。
For EF7 you can use the
hasIndex()
method.We can set clustered and non-clustered index as well.
By default primary key will be clustered . We can change that behavior too.
我发现 @highace 给出的答案存在问题 - 向下迁移对 DropIndex 使用了错误的覆盖。这就是我所做的:
,下面是包含每种方法的两种覆盖示例的代码:
I discovered a problem with the answer @highace gave - the down migration uses the wrong override for DropIndex. Here is what I did:
And here is the code with examples of both overrides of each method:
您可以在模型构建器中指定索引
You can specify index in ModelBuilder