May be an easy one: Limit response on chain relationship call?

If you have the relation setup you can do this

Story::with('photos')->take(10)->get();

I didn't watch the "Project Flyer" series yet, so I'm not sure what you already have in your code. You might want to paste here what you think is necessary for us to help you.

Thank you! That is the call I was trying to remember off the top of my head. That is the call we are currently using, but my understanding is that this call returns ALL photos with each story (story 1 has it's 2 photos, story 2 has it's 4 photos, etc). Is there a way to limit "with('photos')" to only pull the latest photo for each story instead of all photos in the relationship?

I'm on my cell now, but you can pass a array with a closure as an argument to With. That will be passed a query builder instance, and i guess you could order by latest and take one.

UPDATE: Have a look at @thomaskrim for a correct answer.

Take a look here! :) http://laravel.com/docs/5.1/eloquent-relationships#constraining-eager-loads

@jensaronsson Unfortunately, that won't work in this case. I believe that will only retrieve a combined X number of photos rather than X photos per story.

@clkline Take a look at this post to solve your problem: http://softonsofa.com/tweaking-eloquent-relations-how-to-get-n-related-models-per-parent/

First approach: get the last item of the photos collection

    $stories = Story::with('photos')->take(10)->get();

    foreach($stories as $story) {
        echo $story->name, '<br>';
        echo $story->photos->last()->name, '<hr>';
    }

Second approach: Adding another field to your stories table called "default_photo" and set the name of the latests photo.

Well you can pass a closure, something like this

$stories = Story::with(['photos' => function($query) {
    $query->orderBy('created_at', 'desc')->take(1);
}])->take(10)->get();

Note: I didn't tested this! Just to head you in the right direction!

Edit: I tested it, and it works fine ;)

@thomaskim - Thank you for the article! I skimmed it and will read it more fully when I am in "homework mode". That is the concept I am looking for in general, I believe.

@lopezchairez - This is what I thought we were going to have to do - I like the idea of a "default" photo, and I already have in my head how that might work. I will work with my fellow developers on this (and continue to look for any definitive answers here until we are done).

EDIT: @bobbybouwmann - We posted at the same time lol. I think that is what I am going to try to do first. Thank you! Direction was all I needed :D

@bobbybouwmann Your approach will only get one photo and assign it to the last Story

Your code generates the following queries

SELECT * FROM `stories` LIMIT 10
SELECT * FROM `photos` WHERE `photos`.`story_id` in ('1', '2', '3', '4', '5') ORDER BY `created_at` DESC LIMIT 1

@lopezchairez You are correct!

@clkline What you need to do is add a new relation method to your model

public function lastPhoto()
{
    return $this->belongsTo(Story::class)->orderBy('created_at', 'desc')->limit(1);
}

Now you can do this

$stories = Story::with('lastPhoto')->take(10)->get();

@bobbybouwmann I assume lastPhoto goes in the Photo Model, when I run the code I get a BadMethodCallException.

I put the method inside the Story model like so

public function lastPhoto()
{
    return $this->hasMany(Photo::class)->orderBy('created_at', 'desc')->limit(1);
}

But ended up getting one photo assigned to the last Story like before

Yeah you are right again! I'm tired :P hehe

As always Jarek helps us out: http://softonsofa.com/tweaking-eloquent-relations-how-to-get-n-related-models-per-parent/

@bobbybouwmann That's what I linked to earlier. :)

@thomaskim Nice ;)

This made for a fun post-dinner read ROFLOL! Thank you! I will look at this article :)