findOrFail

According to the docs, findOrFail is still avaliable.

http://laravel.com/docs/5.0/eloquent

If it doesn't work,

you can still try firstOrFail() as an alternative.

Hello thank you but it was avaible yesterday before the update. And now with 5.0.2 it can't be found and when i check the file it's no more here as you can see on git it was remove like 2 weeks ago and that fix got implemented into 5.0.2

So how are we supposed to find or fail something now ?

@pmall use firstOrFail() ? or petition it back I suppose.

Well i don't know they removed more function ><

firstOrFail with an id ? What.

@polarcubs firstOrFail doesn't exist too

I just roll back the framework to 5.0.0 for be sure that i didn't made a mistake but yeah all is back

so the issue is on the new release 5.0.2 they removed many things >< so now i'm lost

Anyone knows why these methods are unnecessary ?

Maybe now find === findOrFail ?

It would be cool if now Eloquent gets improved a bit.

It's still there. They just removed the extra one that wasn't necessary.

https://github.com/laravel/framework/blob/master/src/Illuminate/Database/Eloquent/Builder.php#L112

Yes I confirm, I just updated with 5.0.2 and all is working fine ^^

@Creed06

It's still there, only it doesn't make sense at all to have it static on the Model, since it is a method on the Eloquent\Builder class. So feel free to use it and don't worry at all.

Have in mind that every static call to the model is either served by the Model static methods, or by the Eloquent\Builder on the instantiated object, or if no such methods exists, on the Query\Builder. Only then will you get BadMethodCallException, if there is no methods defined on the latter.

Well dunno why first time it doesnt work for me but alter roolback framework to 5.0..0 then update again to 5.0.2 it's work >< weird bug

anyway thank you for your reply guys :)

Didn't know I could throw an array of ids in the find or findOrFail method. Learned something :D

@pmall my bad ;)

@JarekTkaczyk Look at the link jeffrey posted, findOrFail use find and check if there is as many rows as ids.

@pmall Yep, you're right! Hasn't been there before.

This whole time i used whereIn with a check if there is zero items, haha

So I looked in API, it's the signature :

Model|Collection findOrFail(mixed $id, array $columns = array('*'))

You didn't really think Taylor would make such a breaking change in a patch release, did you? Just removing a bit of duplication :)

I was using a trait to catch the fail exception (ModelNotFoundException) and retrow then as TenantModelNotFoundException. In the trait i had a method findOrFail that replaced the parent method that was on the model.

/**
     * Override the default findOrFail method so that we can rethrow a more useful exception.
     * Otherwise it can be very confusing why queries don't work because of tenant scoping issues.
     *
     * @param       $id
     * @param array $columns
     *
     * @throws TenantModelNotFoundException
     */
    public static function findOrFail($id, $columns = ['*'])
    {
        try {
            return parent::findOrFail($id, $columns);
        } catch (ModelNotFoundException $e) {
            throw with(new TenantModelNotFoundException())->setModel(get_called_class());
        }
    }

how can i achieve the same result (parent::findOrFail($id, $columns);) now that findOrFail is not available in the model?

@AlanRezende

// replace
return parent::findOrFail($id, $columns);
// with
return call_user_func_array([static::query(), 'findOrFail'], [$id, $a]);

Thanks @JarekTkaczyk it works perfectly!