StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2017844
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-07T02:31:41.773
FavoriteCount
0
LastActivityDate
2010-01-07T02:31:41.773
LastEditDate
LastEditorUserId
0
OwnerUserId
128896
ParentId
2017793
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> From reading the memory management docs in the SDK, I gathered that factory methods (static constructor methods) would typically be retaining the object for me and adding it to the autorelease pool? </blockquote> Yes, you don't have to worry about releasing objects returned from any method, except the <code>alloc</code>, <code>init</code>, <code>new</code>, and <code>copy</code> methods. <blockquote> This would mean I have no need to retain & release an object as long as the pool does not get released before I expect? </blockquote> Yes. <blockquote> (Which should be at the end of the app, for the default autorelease pool in main()? ) </blockquote> No. You can only count on the object being around until you return from whichever method or function you're in. Typically, autorelease pools are flushed when control returns back to your run loop. If you want an object instance to survive beyond the current method you must take ownership of it, by calling 'retain'. You are then also responsible for 'releasing' the instance when you no longer need it. In your case, if you want your NSMutableArray to stick around, you need to <code>retain</code> it. Better yet, use <code>[[NSMutableArray alloc] initWithCapacity: ];</code> See <a href="http://developer.apple.com/mac/library/documentation/cocoa/Conceptual/MemoryMgmt/Articles/mmPractical.html#//apple_ref/doc/uid/TP40004447" rel="nofollow noreferrer">Practical Memory Management</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQuestion about factory method object lifetimes in Objective-C/Cocoa (to retain or not...)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDarren
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQuestion about factory method object lifetimes in Objective-C/Cocoa (to retain or not...)
 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.