StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20715223
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-21T03:53:16.330
FavoriteCount
0
LastActivityDate
2013-12-21T03:53:16.330
LastEditDate
LastEditorUserId
0
OwnerUserId
2727267
ParentId
20674647
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
According to your update I will propose this: Every time you delete a user who has posts and then try to list their posts <code><%= post.user.name %></code> will return nil because this post no longer has a user to refer to. You can either use the <pre><code>has_many :posts, dependent: :destroy </code></pre> in the User model as I suggested above, or you add some functionality to the deleting of users to prevent errors when trying to view their posts. Some choices are: When a user is deleted you can just delete everything but their name and id in that row of the user table, that will allow you to have <code><%= post.user.name %></code> return a value. When a user is deleted you can delete everything in their User table info and add "-user-deleted" after it kind of like what Tumblr does when a user deactivates their account and their name shows up in a post on some other Tumblr. You can create a User in the DB called "user-deleted" and have that user inherit every post from a user who is deleted. In the User controller add something in your <code>delete</code> action to change the user_id field in their posts to the "user-deleted" account. Or finally you could just check to see if post.user returns a value, and if not just print something like "The user no longer exists in the system" This is all dependent of course on if you even want to allow users to be deleted but still keep their posts. That's certainly a likely case if this is more than just a class project or something you are doing just to learn Rails. Hope this helps. It certainly got me thinking about the pitfalls in allowing users to delete their profiles without having something in place to clean up after them.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy do I get ActionView::Template::Error: undefined method `name' for nil:NilClass on Heroku but not locally
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBeartech
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy do I get ActionView::Template::Error: undefined method `name' for nil:NilClass on Heroku but not locally
 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.