[PATCH] find_or_new

The first diff included changes to the connection settings, could this diff be deleted.

Thanks, sorry for the mishap.

Could you show us a few snippets of application code where this is needed over find_or_create? I'd love to see when this is applicable.

def create

@subscriber = Subscriber.find_or_new_by_email(params[:subscriber][:email]) if @subscriber.id #already signed up, as it has an id

render :partial => 'already'

elsif @subscriber.save

render :partial => 'success'

else

render :partial => 'form'

end

end

For what it's worth, I have implemented a find_or_new in my rails extensions long ago, and occasionally use it.

I think it's good over find_or_create in cases when you just need a temp object with empty/default values, that wouldn't even pass validation if tried to save.

I went looking for this functionality last week when I wanted to use find_or_create, but then modify the resulting object and save it without doing two queries (an INSERT then an UPDATE). Right now, my options are use find_or_create and be happy with two save() calls (one from create, one from my code), or use find() and an if clause. In addition, like Caio said, it would not be difficult to make the object fail validation.

find_or_initialize_by_