我正在使用实体框架从表中删除几个项目。没有外键/父对象，所以我不能用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，对吧?
当前回答
你可以使用像EntityFramework这样的扩展库。Extended或Z.EntityFramework.Plus。EF6，有EF 5, 6或核心可用。当你必须删除或更新时，这些库具有出色的性能，并且它们使用LINQ。删除(source +)的示例:
ctx.Users。Where(x => x. lastlogindate < DateTime.Now.AddYears(-2)) delete ();
或(来源扩展)
context.Users。Where(u => u.FirstName == "firstname") delete ();
它们使用本地SQL语句，因此性能非常好。
其他回答
EF 6.1
public void DeleteWhere<TEntity>(Expression<Func<TEntity, bool>> predicate = null)
where TEntity : class
{
var dbSet = context.Set<TEntity>();
if (predicate != null)
dbSet.RemoveRange(dbSet.Where(predicate));
else
dbSet.RemoveRange(dbSet);
context.SaveChanges();
}
用法:
// Delete where condition is met.
DeleteWhere<MyEntity>(d => d.Name == "Something");
Or:
// delete all from entity
DeleteWhere<MyEntity>();
对于 EC 4.1，
var objectContext = (myEntities as IObjectContextAdapter).ObjectContext;
objectContext.ExecuteStoreCommand("delete from [myTable];");
如果需要删除表中的所有行，可以使用sql命令
using (var context = new DataDb())
{
context.Database.ExecuteSqlCommand("TRUNCATE TABLE [TableName]");
}
TRUNCATE TABLE (Transact-SQL)从表中删除所有行，而不记录单个行删除。TRUNCATE TABLE类似于没有WHERE子句的DELETE语句;然而，TRUNCATE TABLE更快，使用更少的系统和事务日志资源。
这已经够好了，对吧?我可以用扩展来抽象它 方法或助手，但我们还是会用到 foreach ?
是的，不过你可以把它写成两行字:
context.Widgets.Where(w => w.WidgetId == widgetId)
.ToList().ForEach(context.Widgets.DeleteObject);
context.SaveChanges();
实体框架核心
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.
