laravel passing data to view blade

Question

//model
return $this->hasMany('App\Model\Order', 'customer_id')->select('name');

//controller
$customer = Model\customer::find($id);

return view('customer', array('data' => $customer));

//view (blade)
{{ $data }} //{"id":1,"name":"Tony"} 
{{ $data->orders }} //[{"name":"T-shirt"},{"name":"Macbook"}]

i'm new in laravel

I have a question about passing data to view.blade

I used hasMany to join 2 table together and pass $data to view

when I try to output $data, I could not see order object inside of data object

but when I did $data->orders, it shows object

can anyone tell me how it works?

Jeff · Accepted Answer · 2016-11-20 09:49:14Z

1

The behavior you are seeing is because Laravel lazy loads relations when they are accessed. If the relation has not been loaded, Laravel will send another query and add it to your $data object behind the scenes. That's why when you dump the $data variable, you are not seeing the orders.

To demonstrate, run the following snippet.

{{ $data }} //{"id":1,"name":"Tony"} 

// Laravel will lazy load the orders relation
{{ $data->orders }} //[{"name":"T-shirt"},{"name":"Macbook"}]

// Now the $data object has the orders property.
{{ $data }} //{"id":1,"name":"Tony", "orders": [{"name":"T-shirt"},{"name":"Macbook"}]}

Solution

You have a couple options here. Here are 2.

1. Eager load relation when querying model.

$customer = Model\customer::with('orders')->find($id);

This is the preferred method as it prevents n+1 querying.

2. Load relation after model has been queried.

$customer = Model\customer::find($id);

$customer->load('orders');

Now when you dump the model, you will see the orders property.

edited Nov 20, 2016 at 9:49

answered Nov 20, 2016 at 9:27

Jeff

2,0682 gold badges16 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Benjamin W Over a year ago

do I still keep $this->hasMany('App\Model\Order', 'customer_id')->select('name'); inside of my model?

Jeff Over a year ago

Yes, keep it. Also, I made an update to the answer explaining the behavior you are seeing.

Benjamin W Over a year ago

one more question, should I use hasMany to join? or use db builder to create join? $this->select(...)->leftJoin('orders', function($join){...

Benjamin W Over a year ago

hasMany is easier but db builder is more make sense for me

Jeff Over a year ago

Using Eloquent's given relation methods is much better. You have the advantage of shorter query statements, nested relation loading, among many others. So to me, using hasMany would be the preferred method. So, say your Order model also has a relation called Items, To load both relations of the customer, you would simply run Customer::with('orders.items')->find($id).

Nazmul Hasan · Accepted Answer · 2016-11-20 09:00:53Z

0

In your model,

public function orders(){
 return $this->hasMany('App\Model\Order', 'customer_id');
}

In view

{{ $data->orders->order_name }}

I hope it will works

answered Nov 20, 2016 at 9:00

Nazmul Hasan

1,99716 silver badges21 bronze badges

1 Comment

Benjamin W Over a year ago

i understand that, its not what i asking, im asking inside of my blade, i print out $data, why i didn't see orders inside of my object ($data->orders this means orders is part of data)

Arnab Rahman · Accepted Answer · 2016-11-20 09:25:16Z

0

You have defined hasMany relationship in your model. So, for a particular customer there can be multiple orders. So, it shows in array. You have to loop through:

foreach($data->orders as $order)
{
    $order->name
}

to get the orders.

edited Nov 20, 2016 at 9:25

answered Nov 20, 2016 at 9:17

Arnab Rahman

1,0421 gold badge9 silver badges15 bronze badges

1 Comment

Benjamin W Over a year ago

$data->orders this means orders should be inside of data object, when I print out $data, why i couldn't see $orders object inside of $data object

Collectives™ on Stack Overflow

laravel passing data to view blade

3 Answers 3

Solution

1. Eager load relation when querying model.

2. Load relation after model has been queried.

5 Comments

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Solution

1. Eager load relation when querying model.

2. Load relation after model has been queried.

5 Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related