Level 2
I ended up switching to this method
$user = User::where('id', $request->assigned_to)->value('name');
Oct 25, 2018
3
Level 2
findOrFail Returns Incorrect Value
So I'm trying to get the value('name') of a User by there Id. However regardless of what Id I submit with my form it still returns the same value. I am using this method in another controller and it works fine, not sure what I am missing in this situation?
Here is the controller
public function updateCheckedEngagements(Request $request)
{
$engagements = $request->validate([
'engagements' => 'required|array',
'assigned_to' => 'required|integer',
'status' => 'required|string',
]);
$user = User::findOrFail($request->assigned_to)->value('name');
Engagement::whereIn('id', $request->engagements)->update([
'assigned_to' => $user,
'status' => $request->status
]);
$engagements = Engagement::whereIn('id', $request->engagements)->get();
foreach ($engagements as $engagement) {
$engagement->tasks()->update([
'user_id' => $request->assigned_to
]);
};
return response($engagements, 200);
}
I have done a return response($request->assigned_to) to make sure the id I submit is the correct one and it is..
Level 41
@boldstar Your original code is causing issues because of this line:
$user = User::findOrFail($request->assigned_to)->value('name');
The value() method is not a model behavior. It's a query behavior. So essentially, in the original code, by doing this:
->value('name')
You are doing:
select `name` from `users` limit 1
In other words, the value() method is simply fetching the first user. Then you are assigning that object to the $user variable.
What you most likely wanted to do was simply this:
$user = User::findOrFail($request->assigned_to)->name;
This fetches the user by the id and then returns the name, which you assign to the $user variable.
In any case, your new updated code in the second post is the best solution since it doesn't fetch the entire user data. It only fetches and returns the user's name, which seems to be the only thing you need.
1 like
Level 2
@thomaskim, thanks for the reply! I was unaware of the actual sql meaning.
Please or to participate in this conversation.