navigation-properties

问题 Scenario: I'd like to add an entity to the database that would have navigation properties and that entity has navigation properties.. and so on. Basically the tables in the database are connected with each other - all of them. I use EF4.3 and context/request pattern, so I don't want to enable Lazy loading; it would simply just take too much time to load the entity that I need. So far I have learned there is no other way to do it than to use the include method like this: context.Set<TEntity>()

问题 Scenario: I'd like to add an entity to the database that would have navigation properties and that entity has navigation properties.. and so on. Basically the tables in the database are connected with each other - all of them. I use EF4.3 and context/request pattern, so I don't want to enable Lazy loading; it would simply just take too much time to load the entity that I need. So far I have learned there is no other way to do it than to use the include method like this: context.Set<TEntity>()

问题 Using EF Core 1.1.0 I have a model that has collections that themselves have collections. public class A { public string Ay {get;set;} public List<B> Bees {get;set;} } public class B { public string Be {get;set;} public List<C> Seas {get;set;} } public class C { public string See {get;set;} public bool InDark {get;set;} public List<D> Sigh {get;set;} } Now.. A is huge, and 99% of the time I don't care about B, so it doesn't get loaded. If I did load it, then it would be something like:

问题 Using EF Core 1.1.0 I have a model that has collections that themselves have collections. public class A { public string Ay {get;set;} public List<B> Bees {get;set;} } public class B { public string Be {get;set;} public List<C> Seas {get;set;} } public class C { public string See {get;set;} public bool InDark {get;set;} public List<D> Sigh {get;set;} } Now.. A is huge, and 99% of the time I don't care about B, so it doesn't get loaded. If I did load it, then it would be something like:

问题 Using EF Core 1.1.0 I have a model that has collections that themselves have collections. public class A { public string Ay {get;set;} public List<B> Bees {get;set;} } public class B { public string Be {get;set;} public List<C> Seas {get;set;} } public class C { public string See {get;set;} public bool InDark {get;set;} public List<D> Sigh {get;set;} } Now.. A is huge, and 99% of the time I don't care about B, so it doesn't get loaded. If I did load it, then it would be something like:

问题 These are my classes: public class Post : IPost { public int Id { get; set; } public virtual int[] DuplicateOf { get; set; } public virtual ICommentInfo[] Comments { get; set; } } public class CommentInfo : ICommentInfo { public virtual string Author { get; set; } public virtual int Id { get; set; } public virtual string Text { get; set; } public virtual int PostId{ get; set; } [ForeignKey("PostId")] public virtual Post Post { get; set; } } With this CommentConfiguration added to

问题 I have the following PersonelInCourse entity: public partial class PersonnelInCourse { public int ID { get; set; } public string PersonnelID { get; set; } public string CourseID { get; set; } public int HoursInCourse { get; set; } public byte IsApproved { get; set; } public byte IsPassed { get; set; } public Nullable<int> RewardDetailID { get; set; } public string RejectReason { get; set; } public string FailReason { get; set; } public virtual Course Course { get; set; } public virtual

问题 I have the following PersonelInCourse entity: public partial class PersonnelInCourse { public int ID { get; set; } public string PersonnelID { get; set; } public string CourseID { get; set; } public int HoursInCourse { get; set; } public byte IsApproved { get; set; } public byte IsPassed { get; set; } public Nullable<int> RewardDetailID { get; set; } public string RejectReason { get; set; } public string FailReason { get; set; } public virtual Course Course { get; set; } public virtual

问题 When going through a learning article about related entity loading in Entity Framework MSDN, I came across the following: It is also possible to eagerly load multiple levels of related entities . The queries below show examples of how to do this for both collection and reference navigation properties. ...[Examples demonstrating the above]... Note that it is not currently possible to filter which related entities are loaded . Include will always being in all related entities. This seems

问题 When going through a learning article about related entity loading in Entity Framework MSDN, I came across the following: It is also possible to eagerly load multiple levels of related entities . The queries below show examples of how to do this for both collection and reference navigation properties. ...[Examples demonstrating the above]... Note that it is not currently possible to filter which related entities are loaded . Include will always being in all related entities. This seems