Mikael Eliasson
Mikael Eliasson
Similar to #16 Delete by Query but let you update instead. See that issue for more info. I'm not going to suggest a syntax here, just show what EFUtilities does....
When writing extensions for EF it's actually incredibly hard to find out what DB engine is being used. You end up checking the connection which is a problem if that...
Not sure how L2S worked here to start with. I just know how horrible that was in earlier versions of EF. It's much easier if I as an extension author...
One cool thing EF7 will do is to use OUTPUT in Sql Server to support batch inserts even with db generated ids. I have not investigated if any other engines...
Something similar to: ``` db.SetX.DeleteWhere(b => b.Created < limit && b.Title == "T2.0"); ``` The code to generate the filter is already there. The tricky part is that delete is...
Started on issue #41 and #44
Right now EFUtilities can only insert into a single table in each call. That means that an entity with child entities would have to be inserted with two call. ```...
DeleteByQuery, UpdateByQuery, InsertAll, UpdateAll
Improvement 1: Report the batch that fails in the exception Improvement 2: Provide a way to enable finding the exakt row. Binary search through the batch for the first row...