Rails new vs create

ruby-on-rails rest
sent-hil picture sent-hil · Mar 18, 2010 · Viewed 92.6k times · Source

Why is there a need to define a new method in RESTful controller, follow it up with a create method?

Google search didn't provide me the answer I was looking for. I understand the difference, but need to know why they are used the way they are.

Answer

Steve Weet picture Steve Weet · Mar 18, 2010

Within Rails' implementation of REST new and create are treated differently.

An HTTP GET to /resources/new is intended to render a form suitable for creating a new resource, which it does by calling the new action within the controller, which creates a new unsaved record and renders the form.

An HTTP POST to /resources takes the record created as part of the new action and passes it to the create action within the controller, which then attempts to save it to the database.

Related questions

"render :nothing => true" returns empty plaintext file?

I'm on Rails 2.3.3, and I need to make a link that sends a post request. I have one that looks like this: = link_to('Resend Email', {:controller => 'account', :action => 'resend_confirm_email'}, {:method => :post} ) Which makes the …

Read More
Generate a controller with all the RESTful functions

I am trying to generate a controller with all the RESTful actions stubbed. I had read at Wikibooks - Ruby on Rails that all I needed to do was to call the generator with the controller name and I would …

Read More
Rails 4 [Best practices] Nested resources and shallow: true

The following post is based on Rails 4. I am currently looking for a best-practice about the multiple nested resources (more than 1), and the option shallow: true. Initially in my routes, there was this : resources :projects do resources :collections end The …

Read More