If user has model type like following:
public class BaseEntity
{
public string Name { get; set;}
}
public class Product : BaseEntity
{
public int ProductID { get; set; }
}
You can't query on Product as it defines primary key in derived type instead of base type.
Since it's unnecessary to have ID property for queryable attribute to work, why we need this check on base type? We'd better disable the check to make query composition to be more flexible on different user scenarios.
Comments: http://aspnetwebstack.codeplex.com/SourceControl/changeset/5dd998a2c6ca
public class BaseEntity
{
public string Name { get; set;}
}
public class Product : BaseEntity
{
public int ProductID { get; set; }
}
You can't query on Product as it defines primary key in derived type instead of base type.
Since it's unnecessary to have ID property for queryable attribute to work, why we need this check on base type? We'd better disable the check to make query composition to be more flexible on different user scenarios.
Comments: http://aspnetwebstack.codeplex.com/SourceControl/changeset/5dd998a2c6ca