asked on Could you explain how an Laravel's Eloquent result could be used to operate another eloquent query?
Hi Experts
Could you explain how an Laravel's Eloquent result could be used to operate another eloquent query?
This query:
Results in:
[{"metaMensal":"139747.660
After an Eloquent is aplied on the above result
But results in "null".
Is that correctly to use Eloquent this way?
Thanks in advance
Could you explain how an Laravel's Eloquent result could be used to operate another eloquent query?
This query:
$metasMensais = Distribuidormeta::
leftjoin('periodos', 'periodos.id', 'distribuidormetas.periodo_id')
->leftjoin('meses', 'periodos.mes', 'meses.mes')
->where(function($q) use ($distribuidor_id, $distribuidorespermitidos_id){
if($distribuidorespermitidos_id != null && count($distribuidorespermitidos_id) > 0){
$q->whereIn('distribuidor_id', $distribuidorespermitidos_id);
}
if($distribuidor_id != null && $distribuidor_id > 0){
$q->where('distribuidor_id', \DB::raw($distribuidor_id));
}
})
->where('periodos.mes', '>', \DB::raw(1))
->where('periodos.id', \DB::raw($mes_atual))
->groupBy('distribuidormetas.periodo_id')
->select(DB::raw('sum(valor) as metaMensal'), 'periodo_id')
->get();
Results in:
[{"metaMensal":"139747.660
After an Eloquent is aplied on the above result
$metaMes = $metasMensais
->where('periodo_id', \DB::raw(2))
->first();
But results in "null".
Is that correctly to use Eloquent this way?
Thanks in advance
LaravelPHP
Last Comment
Eduardo Fuerte
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Hey Eduardo,
That looks like the correct result to me - what else are you expecting?
In your original post, you say the result of the first query is this:
[{"metaMensal":"139747.660
That's an array containing 1 record.
If you then call the following on it:
$metaMes = $metasMensais
->where('periodo_id', \DB::raw(2))
->first();
Then it's going to pull the first record from that array where periodo_id = 2. As there's only one record, and the periodo_id = 2, it's just going to return that single record:
{"metaMensal":"139747.6600
That looks like the correct result to me - what else are you expecting?
In your original post, you say the result of the first query is this:
[{"metaMensal":"139747.660
That's an array containing 1 record.
If you then call the following on it:
$metaMes = $metasMensais
->where('periodo_id', \DB::raw(2))
->first();
Then it's going to pull the first record from that array where periodo_id = 2. As there's only one record, and the periodo_id = 2, it's just going to return that single record:
{"metaMensal":"139747.6600
ASKER
Hi Chris
Sorry!
Your reply is perfectly correct and solved my issue.
My last post wasn't complete before I sent it.
I was just thinking about the 1st query, without ->get() produces an object where I could apply the 2nd query and inadvertently sent it.
Sorry!
Your reply is perfectly correct and solved my issue.
My last post wasn't complete before I sent it.
I was just thinking about the 1st query, without ->get() produces an object where I could apply the 2nd query and inadvertently sent it.
ASKER
Thank you for the solution!
No worries Eduardo,
Glad I could help
When you're dealing with Eloquent, you're dealing with a QueryBuilder. This means that you can keep on adding methods to adjust the query (where(), limit(), etc). You carry on with a QueryBuilder instance until you call the get() method, or one of the other equivalents (first() etc) - at this point, the QueryBuilder sends the actualy SQL query to the Database and the results are returned. Once you've sent the query, you no longer have the QueryBuilder so you can't then add more methods to it, which is why we add to it before calling get().
Think of the QueryBuilder as a way to prepare your query, and the get() method etc as a way to send the query.
Glad I could help
When you're dealing with Eloquent, you're dealing with a QueryBuilder. This means that you can keep on adding methods to adjust the query (where(), limit(), etc). You carry on with a QueryBuilder instance until you call the get() method, or one of the other equivalents (first() etc) - at this point, the QueryBuilder sends the actualy SQL query to the Database and the results are returned. Once you've sent the query, you no longer have the QueryBuilder so you can't then add more methods to it, which is why we add to it before calling get().
Think of the QueryBuilder as a way to prepare your query, and the get() method etc as a way to send the query.
ASKER
Chris
Clarified!
Very didatic explanation!
Clarified!
Very didatic explanation!
So did I
That results in:
Open in new window