There is no default configuration for eager loading. You must always define Include or create some reusable method which will wrap adding include. For example you can place similar method to your context: public IQueryable<MyEntity> GetMyEntities() { return this.MyEntities.Include(e => e.SomeOtherEntities); }
Try this: Student::with(array(‘exam’ => function($query) { $query->orderBy(‘result’, ‘DESC’); })) ->get();
I think the solution you are asking for is explained here http://softonsofa.com/tweaking-eloquent-relations-how-to-get-latest-related-model/ Define this relation in User model, public function latestAction() { return $this->hasOne(‘Action’)->latest(); } And get the results with User::with(‘latestAction’)->get();
Ok, I wrote an example for myself reflecting your structure and this should work: int projectId = 1; // replace that with the id you want // required for the joins in QueryOver Project pAlias = null; Partner paAlias = null; PartnerCosts pcAlias = null; Address aAlias = null; Money mAlias = null; // Query … Read more
Such feature officially does not exist currently (EF Core 2.0.2 and also the incoming 2.1). It’s been requested in Eager load all navigation properties #4851(Closed) and currently is tracked by Rule-based eager load (include) #2953 and Allow for declaring aggregates in the model (e.g. defining included properties or by some other means) #1985 (both in … Read more
The reason is explained in the Loading Related Data section of the EF Core documentation. The first behavior is because EF Core currently does not support lazy loading, so normally you’ll get null for navigation properties until you specifically load them via eager or explicit loading. However, the Eager loading section contains the following: Tip … Read more
Fetching Collections is a difficult operation. It has many side effects (as you realized, when there are fetched more collections). But even with fetching one collection, we are loading many duplicated rows. In general, for collections loading, I would suggest to use the batch processing. This will execute more SQL queries… but not so much, … Read more
For EF 6 using System.Data.Entity; query.Include(x => x.Collection.Select(y => y.Property)) Make sure to add using System.Data.Entity; to get the version of Include that takes in a lambda. For EF Core Use the new method ThenInclude using Microsoft.EntityFrameworkCore; query.Include(x => x.Collection) .ThenInclude(x => x.Property);