Entity Client

Entity SQL & the EntityClient Provider in ADO.NET vNext

John Papa [MVP C#] — Thu, 15 Feb 2007 04:09:20 GMT

If you watch the ADO.NET team’s blog then you may have seen the post from today from Zlatko Michailov

re: Entity Client

Troy Magennis — Thu, 15 Feb 2007 04:36:48 GMT

Another "SQL like, string based language syntax" seems to be a step backwards in the day and age of LINQ and Expression Trees. Wouldn't a set of LINQ providers formulating queries based upon expression trees solved the same problem and fitted better with the whole LINQ Data != Objects story?

What is the advantage of the "Command Tree" rather than and the standard "Expression Tree"?

Entity SQL - Another string based data-access language

LINQed IN - Troy Magennis' View on .NET, C# and Software Development — Thu, 15 Feb 2007 04:49:58 GMT

This has been bugging me for a while, but I must now admit how disappointed I am that the ADO.Net team...

Entity SQL - Another string based data-access language

LINQed IN - Troy Magennis' View on .NET, C# and Software Development — Thu, 15 Feb 2007 07:51:50 GMT

This is a polarizing post- I really want these issues discussed and debated. I'm interested is anyone...

re: Entity Client

Frans Bouma — Thu, 15 Feb 2007 11:33:54 GMT

"Entity SQL will not support any DML constructs – INSERT, UPDATE, or DELETE in the Orcas release. Data modification could still be done through ObjectContext, or through the native SQL of the target store. "

I find this a bit strange. Entities of the Entity framework mapped as C# classes can be updated/deleted etc. using Linq/objectcontext, but not through eSql ? Isn't it so, that the expression tree resulting from the objectcontext actions is what you should use for eSQL statements?

re: Entity Client

Zlatko Michailov — Fri, 16 Feb 2007 01:50:49 GMT

The requirements for update from object- and entity-level are quite different. Update from object-level (ObjectContext or LINQ) operates over individual object instances. There is a separate command tree for each instance that is being updated. The assumption is: the number of object instances is relatively small compared to the total number of instances in the store.

Entity SQL, on the other hand, operates over entity sets. There should be a single command tree that updates a relatively large set of instances. So object-level update trees are not applicable. Entity-level updates target rather maintenance than application development. By the time maintenance becomes an issue, entity-level updates should be implemented.

New and Notable 142

Sam Gentile — Sun, 18 Feb 2007 19:16:36 GMT

Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software

Insert, Update, Delete support in Entity SQL (ADO.Net Entity Framework)

Guy Burstein's Blog — Fri, 09 Mar 2007 12:53:14 GMT

According to the ADO.Net Team here and here , there will be no support of DML operations in Entity SQL

Entity Framework starting points

ADO.NET, LINQ, DataSet and other fun .NET technology — Fri, 03 Aug 2007 23:18:51 GMT

I was recently asked what a high level list of good starting points for the Entity Framework is. This

ADO.NET team blog : Entity Client

Weddings — Fri, 06 Jun 2008 09:51:43 GMT

With the next release of the .NET Framework, ADO.NET will introduce a new member of the family of data providers – EntityClient . The mission of EntityClient is to provide a gateway for entity-level queries . Through EntityClient one queries against

ADO.NET Entity Framework: Algunos detalles (II)!

Blog del CIIN — Thu, 11 Sep 2008 01:57:22 GMT

Siguiendo con las pruebas de ADO.NET Entity Framework (ADO.NET EF) comenzadas en este post , en esta

New and Notable 142

Sam Gentile's Blog — Wed, 03 Dec 2008 18:16:22 GMT

Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software Architecture/SOA/CAB Udi answers, Can or should SOA be implemented without Web Services? David Chappell on The Three Faces of SOA Eric Newcomer: WS-*