StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1662811
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-11-02T18:15:21.343
FavoriteCount
0
LastActivityDate
2009-11-02T18:15:21.343
LastEditDate
LastEditorUserId
0
OwnerUserId
75245
ParentId
1662772
PostTypeId
2
Score
30
ViewCount
0
LastEditorDisplayName
text
Body
I think it is drawing your attention to the fact that a <code>assign</code> is being used, as opposed to <code>retain</code> or <code>copy</code>. Since an <code>NSString</code> is an object, in a reference-counted environment (ie without Garbage Collection) this can be potentially "dangerous" (unless it is intentional by design). However, the difference between <code>assign</code>, <code>retain</code> and <code>copy</code> are as follows: <ul> <li>assign: In your setter method for the property, there is a simple assignment of your instance variable to the new value, eg: <pre><code>- (void)setString:(NSString*)newString { string = newString; } </code></pre> This can cause problems since Objective-C objects use reference counting, and therefore by not retaining the object, there is a chance that the string could be deallocated whilst you are still using it.</li> <li>retain: this retains the new value in your setter method. For example: <pre><code>- (void)setString:(NSString*)newString { [newString retain]; [string release]; string = newString; } </code></pre> This is safer, since you explicitly state that you want to maintain a reference of the object, and you must release it before it will be deallocated.</li> <li>copy: this makes a copy of the string in your setter method: <pre><code>- (void)setString:(NSString*)newString { if(string!=newString) { [string release]; string = [newString copy]; } } </code></pre> This is often used with strings, since making a copy of the original object ensures that it is not changed whilst you are using it.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONSString no 'assign', 'retain', or 'copy' attribute is specified
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlex Rozanski
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONSString no 'assign', 'retain', or 'copy' attribute is specified
 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
 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.