Find or fail - Strange behaviour

I simply suggest you use firstOrFail() instead of findOrFail().

$order = Order::where('order_id', $order_id)->firstOrFail();

Hope it will work fine.

I don't see anything strange here. If the record couldn't be found in the database, the exception is raised with findOrFail, same for firstOrFail.

Well, there is a bit difference between findOrFail() and firstOrFail(), @jenky

Normally findOrFail() check the field named id in a table. That is why you may get the wrong data.

You may still use findOrFail() but may be overwrite your function a bit. Just check this conversation- https://laracasts.com/discuss/channels/general-discussion/findorfail?page=2

@tisuchi yeah, i know the difference, but from his code.

$order = Order::findOrFail($order_id);

I think the $order_id is the value of the id field in the table.

findOrFail() won't check for 'the field named id' in a table, it'll look for the passed value within the specified primary column of a table, whether that's 'id' (by default) or 'thisIsMyPrimaryKey'.

I wouldn't recommend using firstOrFail() it seems like that's addressing the consequence and not the issue.

if for any reason the primary key on the table isn't 'id', you should set it up in the Model and that should make findOrFail() work as expected.