StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13859920
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-13T12:30:10.403
FavoriteCount
0
LastActivityDate
2012-12-13T13:22:29.577
LastEditDate
2012-12-13T13:22:29.577
LastEditorUserId
1187415
OwnerUserId
1187415
ParentId
13859068
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
See <a href="https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MemoryMgmt/Articles/mmRules.html" rel="nofollow">Memory Management Policy</a> in the "Advanced Memory Management Programming Guide": <blockquote> You own any object you create You create an object using a method whose name begins with “alloc”, “new”, “copy”, or “mutableCopy” (for example, alloc, newObject, or mutableCopy). You must not relinquish ownership of an object you do not own </blockquote> These rules are consistent with methods compiled with ARC. In the <a href="http://clang.llvm.org/docs/AutomaticReferenceCounting.html" rel="nofollow">ARC documentation</a>, the behaviour of methods in the first category is described in "3.2.2. Retained return values": <blockquote> When returning from such a function or method, ARC retains the value at the point of evaluation of the return statement, ... </blockquote> which means that the caller must release the object. Methods in the second category are described in "3.2.3. Unretained return values": <blockquote> When returning from such a function or method, ARC retains the value at the point of evaluation of the return statement, then leaves all local scopes, and then balances out the retain ... </blockquote> which means the the caller must not release the object. So in your example: <pre><code>LibObject* obj1 = [[LibObject alloc] init]; LibObject* obj2 = [obj1 otherObj]; [obj1 release]; //should I release it? --> YES [obj2 release]; //should I release it? --> NO </code></pre> You own <code>obj1</code>, because it was created with <code>alloc</code>, so you have to release <code>obj1</code>. You don't own <code>obj2</code>, therefore you must not release it. Note: If you run the Xcode static analyzer on your code, it shows exactly where these rules are violated.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCalling ARC method from non-ARC code
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMartin R
UserOwnerUserId
1. USMartin R
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCalling ARC method from non-ARC code
 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.