Laravel - relationship 1 for two tables and sort

Asked

Viewed 95 times

0

I have a playlist table, a playlist_content table and two Vodcontent and Livecontent tables.

Today I make the relationship between vodcontent and livecontent with a hasManyThrough relationship. $this->hasManyThrough(Vodcontent::class, Playlistcontent::class, playlist_id', 'content_id', 'id', 'content_id');

When I list the contents of the playlist, I would like to sort in an order field that is in the intermediate table, playlist_content, only that if I put order by in each relationship (Vod and live), when I merge to display all live content, That’s where it creates the problem, it will pick up in order, but prioritizing through the merge. I thought Collection do a Sort by order, but it does not return the field of this intermediate column, it would have some way to get the column of the intermediate table?

Trying to simplify how it would be visualized. VOD has content in order 1, 3 and Live has content in order 2 With the merge to display the results, if I put Vod as first and live in second, it ends up returning 1,3,2. The correct order would be 1,2,3 in this example.

Relationships in the Playlist model

public function live_contents() {
  return $this->hasManyThrough(LiveContent::class, PlaylistContent::class, 'playlist_id', 'content_id', 'id', 'content_id')->orderBy("order");
}

public function vod_contents() {    
  return $this->hasManyThrough(VODContent::class, PlaylistContent::class, 'playlist_id', 'content_id', 'id', 'content_id')->orderBy("order"); 
}

For the list of contents with merge

$contents = new Collection($playlist->vod_contents()->paginate());
$livecontents = new Collection($playlist->live_contents()->paginate());
$collection = $contents->merge($livecontents);
return collect($collection);
php laravel

  • Your modeling seems strange to me, you have two tables of Contents when you could only have one and indicate a content_type flag. As for this code I see that you have merged into two paginated Collections, the result will not be the two Collections data with a new pagination but the two Paginations together. I may not have read it right.

  • Yes, I’m still thinking of improving this modeling, soon joining the vodcontents table and livecontents (which both also have the content type to make another differentiation). Anyway, I think in the place of paginate is get even, maybe I copied from some test.

1 answer

0

Dude, this is how this relationship works:

In the playlist model:

public function live_contents() {

   return $this->hasMany(LiveContent::class, 'playlist_id', 'id')->orderBy('order', 'DESC'); //Você escolhe a ordem, ASC ou DESC

}

public function vod_contents() {

  return $this->hasMany(VodContent::class, 'playlist_id', 'id')->orderBy('order','ASC') //Você escolhe a ordem, ASC ou DESC
}

On the controller:

$playlists = Playlist::with('live_contents', 'vod_contents')->paginate(10);

In view:

@foreach($playlists as $playlist)
     {{dd($playlist->live_contents, $playlist->vod_contents)}}
@endforeach

Just to test and be happy

Browser other questions tagged php laravel

You are not signed in. Login or sign up in order to post.