entity-framework-4.1

We are using EF 4.1 and the fluent API to get data from a legacy database (that we are not permitted to change). We are having a problem creating a relationship between two tables where the related columns are not primary and foreign keys. With the classes below, how would we configure the one-to-many relationship between Report and RunStat such that Report.RunStats would return all of the RunStat entities where the ReportCode fields are equal? public class Report { [Key] public int ReportKey { get; set; } public string Name { get; set; } public int ReportCode { get; set; } // Can we associate

I'm using Entity Framework 4.1 database first approach. I've used legacy database. In my edmx file which created entity classes based on tables in the legacy database, there is a one-to-zero-or-one association between some entities. Although I explored the tables of database and relation between them I didn't find out how one-to-zero-or-one relation have been implemented in database. For more information I put some screenshots of my database diagram and the property of its relation and correspondent entities in edmx file: The 1-0..1 relation in your database is directly visible. It is built

I've been looking at Applying filters when explicitly loading related entities and could not get it to work for a many-to-many relationship. I created a simple model: Brief description: A Student can take many Courses and a Course can have many Students . A Student can make many Presentation , but a Presentation can be made by only one Student . So what we have is a many-to-many relationship between Students and Courses , as well as a one-to-many relationship between Student and Presentations . I've also added one Student , one Course and one Presentation related to each other. Here is the

Is there a standard way to using Enums in EF code-first? There seems to be some examples making use of a wrapper class for the enum. However, I would like to be able to define the enum and have the enum values also seeded into the database using the database initializer. There doesn't seem to be much point in defining the enum and creating a wrapper, if I then have to seed the database table manually from the enum. VinnyG Now supported : http://blogs.msdn.com/b/adonet/archive/2011/06/30/announcing-the-microsoft-entity-framework-june-2011-ctp.aspx The Microsoft Entity Framework June 2011 CTP

I have an application where you can create a new type of product and add to that product some ingredients. The product and the ingredients are both entities saved in a database. The product entity has a collection of ingredient entities. (simplified version) public class Product Public Sub New() Me.Ingredients = New List(Of Ingredient)() End Sub Property Ingredients as ICollection(Of Ingredient) end class When I save the product for the first time, all goes well: I just add it to the context and call SaveChanges. myDataContext.Products.Add(product) myDataContext.SaveChanges() Both the product

I would like know what is the best possible way to implement transactions with DBContext . In particular, Does DbContext.SaveChanges implement transaction internall if i change multiple entities? If i want to call DbContext.SaveChanges multiple times(same contxet/different contxets), how transaction can be achieved? Ladislav Mrnka Yes. SaveChanges uses transaction internally. Use TransactionScope to wrap multiple calls to SaveChanges Example: using(var scope = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadCommitted })) { //