StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7246324
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-30T16:13:16.067
FavoriteCount
0
LastActivityDate
2011-08-30T16:13:16.067
LastEditDate
LastEditorUserId
0
OwnerUserId
385622
ParentId
3346116
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I can understand why Craig missed that actually. It's such a subtle difference it didn't even cross my mind. The only thing that tipped me off is that my named routes for the singleton resource has a weird index name: <code>user_foo_index</code> instead of <code>user_foos</code>. It's a really smart deduction from the absence of plural on the part of Rails. Warning: The following examples use shallow nesting by either doing this: <pre><code>resources :cats, shallow: true do resources :noms end </code></pre> Or that: <pre><code>resources :cats do shallow do resources :noms end end </code></pre> Anyway back to business, if you setup a singular resource – <code>address</code> as opposed to <code>articles</code> for instance – and you see something like this: <pre><code>user_address_index GET | POST new_user_address GET edit_address GET address GET | PUT | DELETE </code></pre> Then as Andreas justly pointed out, you probably incorrectly declared this in your routes: <pre><code>resources :users do resources :address end </code></pre> And if you change that to: <pre><code>resources :users do resource :address end </code></pre> You should be all fine and happy and see something like this if you punch <code>rake routes</code> in your prompt: <pre><code> user_address POST | GET | PUT | DELETE new_user_address GET edit_user_address GET </code></pre> Note: I know the output of rakes routes doesn't look exactly like this (it's a lot more verbose), I'm just simplifying for the sake of focus. Hope that helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORails 3 has_one routing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOlivier Lacan
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.