Pluralization

Unfortunately in the current version of the Entity Framework, which ships in .NET 3.5 SP1, we don’t make any attempt to Singularize or Pluralize names when reverse engineering a model from the database. So if, for example, your database has a table called Orders you will get an EntityType called Orders too, which clearly doesn’t make for…

13

N-Tier Improvements for Entity Framework

The first version of Entity Framework provides convenient ways to load, manipulate and persist objects and relationships. As with many other O/RMs, Entity Framework has a state manager that tracks every change made. Existing objects are typically loaded first from the database, later modified, and finally the changes are saved back to the store. Another…

54

Foreign Keys in the Conceptual and Object Models

If you are reading this, you have probably heard by now about the so called impedance mismatch between the relational world and the object world – and there are a number of concepts in the relational database that don’t translate easily to corresponding concepts supported by the object oriented paradigm. One of these factors that…

37

EDM and Store functions exposed in LINQ

In this post Colin Meek and Diego Vega delve into some enhancements we are planning for LINQ to Entities, anyway over to them… Entity Framework v1 customers preferring to write their queries using LINQ often hit a limitation on the range of functions and query patterns supported in LINQ to Entities. For some of those…

14

Model First

One of the most painful omissions from the Entity Framework V1 was Model First, which basically means creating a conceptual ‘model first’ and then deriving a storage model, database and mappings from that. People ask for this scenario all the time in the forums. Well Noam, a Program Manager on the Entity Framework Tools team,…

42

Structural Annotations – One Pager

In V1 of the Entity Framework it is possible to annotate a schema using attributes declared in another XSD. However XML attributes are a very limited form of annotation. It would be better if we could annotate using full elements. This is what we are calling Structural Annotations. This feature will allow both customers and…

3

Discussion about API changes necessary for POCO:

Evolving an API to support new requirements, like POCO, while maintaining backward compatibility is challenging. The following design discussion from members of the Object Services team illustrates some of the issues and hard calls involved. Have a read, and tell us what you think. In particular are we missing something, or overstating the importance of…

20

Using Stored Procedures to load structured data.

V1 of the Entity Framework allows you to use stored procedures in two main ways: Mapping Create, Update and Delete entity operations to appropriate stored procedures. Doing a FunctionImport that allows you to return an enumeration of Entities* Now the thing is, in order to return an enumeration of Entities, you have to map the Entity…

9

Transparent Caching Support in the Entity Framework

The Entity Framework’s provider model makes it possible for it to work over different database’s. The idea being that someone, either the database vendor or a third party, can write a provider that allows the Entity Framework to work with that database. The Entity Framework asks the provider to convert queries and update operations from a…

14

Computed Properties One Pager

UPDATE: this blog post is out of date. Please review this instead.  If you’ve been paying attention to what the Entity Framework team has been saying. You will remember hearing us talk about using the Entity Data Model (EDM) as a common way of describing models that can be understood by many different applications. As of…

17