StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2673040
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-04-20T06:30:08.757
FavoriteCount
0
LastActivityDate
2010-04-21T05:10:49.337
LastEditDate
2010-04-21T05:10:49.337
LastEditorUserId
182849
OwnerUserId
182849
ParentId
2672521
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
If you're following the RESTFUL resource conventions you might want use: <pre><code>map.resources :system, :has_many => :title, :path_prefix => '/store/' </code></pre> This would generate handy little routes that could prove very helpful: <pre><code>system_title_index GET /store/system/:system_id/title(.:format) {:controller=>"title", :action=>"index"} POST /store/system/:system_id/title(.:format) {:controller=>"title", :action=>"create"} new_system_title GET /store/system/:system_id/title/new(.:format) {:controller=>"title", :action=>"new"} edit_system_title GET /store/system/:system_id/title/:id/edit(.:format) {:controller=>"title", :action=>"edit"} system_title GET /store/system/:system_id/title/:id(.:format) {:controller=>"title", :action=>"show"} PUT /store/system/:system_id/title/:id(.:format) {:controller=>"title", :action=>"update"} DELETE /store/system/:system_id/title/:id(.:format) {:controller=>"title", :action=>"destroy"} system_index GET /store/system(.:format) {:controller=>"system", :action=>"index"} POST /store/system(.:format) {:controller=>"system", :action=>"create"} new_system GET /store/system/new(.:format) {:controller=>"system", :action=>"new"} edit_system GET /store/system/:id/edit(.:format) {:controller=>"system", :action=>"edit"} system GET /store/system/:id(.:format) {:controller=>"system", :action=>"show"} PUT /store/system/:id(.:format) {:controller=>"system", :action=>"update"} DELETE /store/system/:id(.:format) {:controller=>"system", :action=>"destroy"} /:controller/:action/:id </code></pre> Your URL will look slightly different though:<code>/store/system/xbox360/title/Mass%20Effect</code> Remember to override the <code>to_param</code> method in your system and title models so that the id would be the actual names of the object instead of just numbers. Hope this helps! 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails routing to /store/:system/:title
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjonasespelita
UserOwnerUserId
1. USjonasespelita
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORails routing to /store/:system/:title
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.