我正在使用实体框架从表中删除几个项目。没有外键/父对象，所以我不能用OnDeleteCascade处理这个。
现在我正在做这个:
var widgets = context.Widgets
.Where(w => w.WidgetId == widgetId);
foreach (Widget widget in widgets)
{
context.Widgets.DeleteObject(widget);
}
context.SaveChanges();
它工作，但foreach困扰我。我使用EF4，但我不想执行SQL。我只是想确保我没有错过任何东西-这是最好的，对吧?我可以用扩展方法或helper来抽象它，但在某些地方我们还是要用foreach，对吧?
当前回答
Thanh的回答最适合我。在一次服务器访问中删除了我所有的记录。我挣扎着实际调用扩展方法，所以我想分享我的(EF 6):
我将扩展方法添加到我的MVC项目中的一个助手类中，并将名称更改为“RemoveWhere”。我在控制器中注入了一个dbContext，但你也可以做一个using。
// make a list of items to delete or just use conditionals against fields
var idsToFilter = dbContext.Products
.Where(p => p.IsExpired)
.Select(p => p.ProductId)
.ToList();
// build the expression
Expression<Func<Product, bool>> deleteList =
(a) => idsToFilter.Contains(a.ProductId);
// Run the extension method (make sure you have `using namespace` at the top)
dbContext.RemoveWhere(deleteList);
这将为组生成一条delete语句。
其他回答
EF 6.=>
var assignmentAddedContent = dbHazirBot.tbl_AssignmentAddedContent.Where(a =>
a.HazirBot_CategoryAssignmentID == categoryAssignment.HazirBot_CategoryAssignmentID);
dbHazirBot.tbl_AssignmentAddedContent.RemoveRange(assignmentAddedContent);
dbHazirBot.SaveChanges();
using (var context = new DatabaseEntities())
{
context.ExecuteStoreCommand("DELETE FROM YOURTABLE WHERE CustomerID = {0}", customerId);
}
新增:支持可编写的id列表
var listOfIds = String.Join(',',customerIds.Select(id => $"'{id}'").ToList());
var sql= $@"DELETE [YOURTABLE] WHERE CustomerID in ({listOfIds})";
注意:如果CustomerID是一个字符串，您应该仔细检查潜在的SQL注入风险，对于整数CustomerID是安全的
实体框架核心
3.1 3.0 2.2 2.1 2.0 1.1 1.0
using (YourContext context = new YourContext ())
{
var widgets = context.Widgets.Where(w => w.WidgetId == widgetId);
context.Widgets.RemoveRange(widgets);
context.SaveChanges();
}
简介:
从集合下面的上下文中移除给定的实体集合 每个实体都处于已删除状态，这样它就会被删除 当SaveChanges被调用时，从数据库中获取。
备注:
Note that if System.Data.Entity.Infrastructure.DbContextConfiguration.AutoDetectChangesEnabled is set to true (which is the default), then DetectChanges will be called once before delete any entities and will not be called again. This means that in some situations RemoveRange may perform significantly better than calling Remove multiple times would do. Note that if any entity exists in the context in the Added state, then this method will cause it to be detached from the context. This is because an Added entity is assumed not to exist in the database such that trying to delete it does not make sense.
对于 EC 4.1，
var objectContext = (myEntities as IObjectContextAdapter).ObjectContext;
objectContext.ExecuteStoreCommand("delete from [myTable];");
如果你不想直接执行SQL，在循环中调用DeleteObject是最好的方法。
但是，您可以使用我在这里描述的方法，通过扩展方法执行SQL，并使其完全通用。
尽管答案是3.5。对于4.0，我可能会在底层使用新的ExecuteStoreCommand API，而不是下拉到StoreConnection。
