Comments on: Trusting in Exceptions To Do What They Do

By: rick

rick — Tue, 02 Jan 2007 20:31:19 +0000

I think using rescue_action_in_public is a good, DRY way to handle this. I also use just rescue_action to handle common ActiveRecord::RecordInvalid exceptions by rendering either the ‘new’ or ‘edit’ template.

By: Adam

Adam — Mon, 04 Dec 2006 10:26:53 +0000

Forgot about that way. Thanks.

I was not familiar with @verify@ however. That is a pretty useful method as well, but since I’ve moved to using the RESTful stuff in rails 1.2RC1, That kind of stuff already happens for me, with the IDs and whathave you. Plus, @verify@ is only a first step, it does not verify that your data exists and something like the @rescue@ or your conditional statement is still necessary.

@rescue_action_in_public@ is a neat method; however, I often reserve that method for “Exception Logger”:http://svn.techno-weenie.net/projects/plugins/exception_logger/

By: Maxim Kulkin

Maxim Kulkin — Sun, 03 Dec 2006 23:27:23 +0000

There is also another solution:

  def show
    @article = Article.find_by_id(params[:id])
    unless @article
      flash[:error] = 'That article does not exist'
      redirect_to :action => 'index'
    end
  end

And don't forget about verify method that could be used to make sure that user passed non-empty id param to that action.

Although I would prefer ot put such rescue clauses in separate place (e.g. rescue_action_in_public).