StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16500469
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-05-11T18:35:19.810
FavoriteCount
0
LastActivityDate
2013-05-11T18:35:19.810
LastEditDate
LastEditorUserId
0
OwnerUserId
457406
ParentId
16499101
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
First of all, you are not calling <code>[super prepareForReuse]</code> like you should. And the documentation is pretty clear, you should be setting the image in <code>tableView:cellForRowAtIndexPath:</code> because it's content. If you set the image in <code>tableView:cellForRowAtIndexPath:</code> there is no point to set it to nil in <code>prepareForReuse</code>. Imagine the following flow. <ol> <li>You scroll down, cell 0 is put onto the queue. </li> <li><code>prepareForReuse</code> sets imageView.image to nil</li> <li><code>tableView:cellForRowAtIndexPath:</code> dequeues the cell and sets imageView.image to image1</li> </ol> You are setting imageView.image twice. If you use nil there might be no measurable performance impact at all. But you might come to the idea to actually set a placeHolder image. So the cell is queued and prepared for reuse, you set the placeholder image; later the cell is dequeued and the placeholder image is replaced by a real image before the placeholder image was even visible. I would remove the <code>prepareForReuse</code> method completely. You don't need it if you set the image in <code>tableView:cellForRowAtIndexPath:</code> <hr> from the <a href="http://developer.apple.com/library/ios/documentation/uikit/reference/UITableViewCell_Class/Reference/Reference.html#//apple_ref/doc/uid/TP40006938-CH3-SW33" rel="nofollow">documentation</a>: <blockquote> If a UITableViewCell object is reusable—that is, it has a reuse identifier—this method is invoked just before the object is returned from the UITableView method dequeueReusableCellWithIdentifier:. For performance reasons, you should only reset attributes of the cell that are not related to content, for example, alpha, editing, and selection state. The table view's delegate in tableView:cellForRowAtIndexPath: should always reset all content when reusing a cell. If the cell object does not have an associated reuse identifier, this method is not called. If you override this method, you must be sure to invoke the superclass implementation. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTable View Cell With Image
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatthias Bauch
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTable View Cell With Image
 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
 VTAcceptedByOriginator
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.