entity-framework-4.1

I am trying to implement caching mechanism for entities. And to use the entities correctly and seamlessly with the caching i need to detach the entity from the current context before i put it in a cache and attach it back the the new context when i get it from the cache. (My context lifetime is per http request) The requirements are that - All the navigational properties that are associated with it (which i have already populated) should not be removed when the entity is detached. I can update the cached items if i want ( so correctly attaching them to the new context is important). This is my

When using data annotations with EF4.1 RC is there an annotation to cause cascade deletes? public class Category { public int Id { get; set; } [Required] public string Name { get; set; } public ICollection<Product> Products { get; set; } } public class Product { public int Id { get; set; } public string Name { get; set; } public Category Category { get; set; } } Using this model the constraint generated is: ALTER TABLE [Product] ADD CONSTRAINT [Product_Category] FOREIGN KEY ([Category_Id]) REFERENCES [Categorys]([Id]) ON DELETE NO ACTION ON UPDATE NO ACTION; If not how is it achieved? Putting

Is there a way to make the EFTracing provider work with EF 4.1? EFTracing seems to need an objectcontext and I use dbcontext. Thanks in advance! Yes, you can. I'm using the community version with both database-first DbContexts and code-first DbContexts. This answer is based on a discussion thread on the project site. For database-first/designer DbContexts (via ADO.NET DbContext Generator templates ), you can simply add the following constructor: public abstract class MyDbContext : DbContext { protected MyDbContext(string nameOrConnectionString) : base(EFTracingProviderUtils

I'm working on a small sample project using Entity Framework 4.1 (code first). My classes look like this: public class Context : DbContext { public IDbSet<Person> People { get; set; } public IDbSet<EmployeeType> EmployeeTypes { get; set; } } public class Person { [Key] public int Key { get; set; } public string FirstName { get; set; } public string LastName { get; set; } virtual public EmployeeType EmployeeType { get; set; } } public class EmployeeType { [Key] public int Key { get; set; } public string Text { get; set; } virtual public ICollection<Person> People { get; set; } } I've saved a

I am designing my database using code first and I need a little help I think. I am getting this error: Introducing FOREIGN KEY constraint 'SalesOrder_Invoices' on table 'Invoices' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other FOREIGN KEY constraints. Could not create constraint. See previous errors. I am trying to have the following relationships/keys: --> = 1 to Many Relationship Customer --> CustomerLocation CustomerLocation --> SalesOrder SalesOrder --> Invoice SalesRep --> SalesOrder PaymentTerm --> Customer PaymentTerm -->