The entity cannot be constructed in a LINQ to Entities query

Question

There is an entity type called Product that is generated by entity framework. I have written this query

public IQueryable<Product> GetProducts(int categoryID) {     return from p in db.Products            where p.CategoryID== categoryID            select new Product { Name = p.Name}; } 

The code below throws the following error :

"The entity or complex type Shop.Product cannot be constructed in a LINQ to Entities query"

var products = productRepository.GetProducts(1).Tolist(); 

But when I use select p instead of select new Product { Name = p.Name}; it works correctly.

How can I preform a custom select section?

Answer 1

You cannot (and should not be able to) project onto a mapped entity. You can, however, project onto an anonymous type or onto a DTO:

public class ProductDTO {     public string Name { get; set; }     // Other field you may need from the Product entity } 

And your method will return a List of DTO's.

public List<ProductDTO> GetProducts(int categoryID) {     return (from p in db.Products             where p.CategoryID == categoryID             select new ProductDTO { Name = p.Name }).ToList(); } 

Answer 2

You can project into anonymous type, and then from it to model type

public IEnumerable<Product> GetProducts(int categoryID) {     return (from p in Context.Set<Product>()             where p.CategoryID == categoryID             select new { Name = p.Name }).ToList()            .Select(x => new Product { Name = x.Name }); } 

Edit: I am going to be a bit more specific since this question got a lot of attention.

You cannot project into model type directly (EF restriction), so there is no way around this. The only way is to project into anonymous type (1st iteration), and then to model type (2nd iteration).

Please also be aware that when you partially load entities in this manner, they cannot be updated, so they should remain detached, as they are.

I never did completely understand why this is not possible, and the answers on this thread do not give strong reasons against it (mostly speaking about partially loaded data). It is correct that in partially loaded state entity cannot be updated, but then, this entity would be detached, so accidental attempts to save them would not be possible.

Consider method I used above: we still have a partially loaded model entity as a result. This entity is detached.

Consider this (wish-to-exist) possible code:

return (from p in Context.Set<Product>()         where p.CategoryID == categoryID         select new Product { Name = p.Name }).AsNoTracking().ToList(); 

This could also result in a list of detached entities, so we would not need to make two iterations. A compiler would be smart to see that AsNoTracking() has been used, which will result in detached entities, so it could allow us to do this. If, however, AsNoTracking() was omitted, it could throw the same exception as it is throwing now, to warn us that we need to be specific enough about the result we want.