StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9112726
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-02T12:58:26.997
FavoriteCount
0
LastActivityDate
2014-07-22T20:58:52.023
LastEditDate
2017-05-23T12:27:29.383
LastEditorUserId
-1
OwnerUserId
1059843
ParentId
9112439
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> The PagesController becomes a StaticPagesController </blockquote> There is no reason. PagesController is fine. He did that maybe for clarity reason (?). <blockquote> @Title is not anymore initialised in the controller, but in each page </blockquote> This is for best practice/convention reason. Please take a look at the answer on this question <a href="https://stackoverflow.com/questions/8590406/where-does-the-meta-content-live-in-the-mvc/8593728#8593728">Where does the meta content live in the MVC?</a> <blockquote> The @Title variable is initialised through "provide" function, and used through "yield" function instead of simply inserting <%= @title %> </blockquote> Same answer as above. Some people think that meta content such as title belongs to the view and thus should be set in the view, not in the controller. The practical differences between <code>provide</code> and <code>content_for</code> are well explained here: <a href="http://api.rubyonrails.org/classes/ActionController/Streaming.html#module-ActionController::Streaming-label-Communication+between+layout+and+template" rel="nofollow noreferrer">http://api.rubyonrails.org/classes/ActionController/Streaming.html#module-ActionController::Streaming-label-Communication+between+layout+and+template</a> Please note that these changes are not specific to Rails 3.2 (except for <code>provide</code> that was introduce with <code>stream</code> in Rails 3.1).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMichael Hartl's book differencies between Rails 3.0 and Rails 3.2
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USDamien
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMichael Hartl's book differencies between Rails 3.0 and Rails 3.2
 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
 VTUpMod
3. 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.