StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5139154
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-02-28T07:16:49.990
FavoriteCount
0
LastActivityDate
2011-02-28T07:16:49.990
LastEditDate
LastEditorUserId
0
OwnerUserId
165737
ParentId
5138371
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Adding a helper function for each specific page does seem like a code smell in this case. It may not always be a problem if you were referring say <code>user.second_wall</code> very often and needed a quick way to get to it. However, by linking each such function, <pre><code>read_wall -> second_wall -> third_wall -> fourth_wall </code></pre> it will become incrementally hard to expand and maintain this. Maybe have a base function that can retrieve the wall posts given any user and the desired range. <pre><code>get_wall_posts(user_id, range) </code></pre> To get the first 100 wall posts, and mapping the id's would look something like, <pre><code>first_100_posts = get_wall_posts(some_user, 0...100); first_100_ids = first_100_posts.map { |post| post['id'] } </code></pre> One of the most important part of refactoring is to give good names to identifiers. Names such as <code>var</code> and <code>iterate</code> usually don't say much about the code. It is similar to, if not worse, than comments like, <pre><code>// increment i by 1 i++; </code></pre> Consistency is just as important. Groups of methods that do similar things should be named in a consistent manner. <code>read_wall</code> and <code>second_wall</code> seem to have a disconnect for me because the verb <code>read</code> missing from the other methods. <code>read_second_wall</code> sounds like a better name, and more inline with the rest. Another thing to consider in mind with the current design is object consistency. Currently some of the methods are linked by a process (getting the first 100 or 4 pages worth of posts) and not by their individual role, making them dependent on each other. Calling <code>second_wall</code> without calling <code>read_wall</code> will yield different results because the <code>result</code> property has not been initialized yet. That can result in difficult to find bugs because there is another dimension to keep track of - whether object are used in the order expected. Try to limit the side-effects of functions as much as possible. If an objected must be used in a certain order, then use the <a href="http://en.wikipedia.org/wiki/State_pattern" rel="nofollow"><code>state</code></a> pattern or anything similar to ensure that.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POI've created a disaster. Please point out a coding strategy to refactor this
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAnurag
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. This table or related slice is empty.
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.