why use rescue nil?

[John Merlino]

Hey all,

I saw this piece of code:

@user = User.find(params[:user_id]) rescue nil

why rescue with a nil here? If the user is not found, it will be nil
anyway.

[Fernando Almeida]

if the record is not found the find() throws an exception.

2012/6/19 John Merlino <stoi...@aol.com>

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.

--
Fernando Almeida
www.fernandoalmeida.net

[Fernando Almeida]

http://api.rubyonrails.org/classes/ActiveRecord/RecordNotFound.html

2012/6/19 Fernando Almeida <fern...@fernandoalmeida.net>

--
Fernando Almeida
www.fernandoalmeida.net

[John Merlino]

ok I thought it would return nil

thanks for response

On Jun 19, 8:33 pm, Fernando Almeida <ferna...@fernandoalmeida.net>
wrote:

> if the record is not found the find() throws an exception.
>

> 2012/6/19 John Merlino <stoici...@aol.com>

[Michael Pavling]

On 20 June 2012 01:55, John Merlino <stoi...@aol.com> wrote:
> ok I thought it would return nil

It would take 30seconds to try it out in a console...

[Alex Mercer]

Alson you could just use where:
  @user = User.where(:id => params[:user_id]).first

[Matt Jones]

On Tuesday, 19 June 2012 20:29:25 UTC-4, John Merlino wrote:

Hey all,

I saw this piece of code:

@user = User.find(params[:user_id]) rescue nil

why rescue with a nil here? 

Because the author forgot about find_by_id, which would accomplish the exact same thing (returning nil if no record was found).

--Matt Jones 

[Mirri Kim]

Just a reminder: it's just specific with the find(). find_by_* will return nil unless you add a ! (e,g,, find_by_name!()) then it also returns the exception