StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5527309
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-04-03T03:09:43.040
FavoriteCount
0
LastActivityDate
2011-04-03T03:16:42.907
LastEditDate
2011-04-03T03:16:42.907
LastEditorUserId
589985
OwnerUserId
589985
ParentId
5347917
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You can set up the routing manually, if you're that concerned about what URL is going to show. For what you want, you can have a <code>GET</code> to <code>/foos/new</code> render your form, and a <code>POST</code> to the same URL do the creation: <pre><code>map.with_options :controller => :foos do |foo| foo.new_foo '/foos/new', :conditions => {:method => :get}, :action => :new foo.create_foo '/foos/new', :conditions => {:method => :post}, :action => :create foo.foos '/foos', :conditions => {:method => :get}, :action => :index end </code></pre> This should work without requiring any changes to your controller (yay!) - all three actions from your example are taken care of. The few disclaimers: <ol> <li>This is based on my routing for a 2.3.8 app - some syntax (semantics?) changes are probably required to get it into Rails 3 routing style.</li> <li>My attempts to mix this style of routing with <code>map.resources</code> have failed horribly - unless you're more familiar with this than me, or Rails 3 routing is better (both easily possible), you'll have to do this for every route to the controller.</li> <li>And finally, don't forget to add <code>/:id</code>, <code>(.:format)</code>, etc. to the routes that need them (none in this example, but see #2).</li> </ol> Hope this helps! Edit: One last thing - you'll need to hard-code the URL in your <code>form_for</code> helper on <code>/foos/new.html.erb</code>. Just add <code>:url => create_foo_path</code>, so Rails doesn't try to post to <code>/foos</code>, which it will by default (there might be a way to change the creation URL in the model, but I don't know of it, if there is one).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails: URL after validation fails when creating new records via form
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USXavier Holt
UserOwnerUserId
1. USXavier Holt
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.