StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
855629
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-05-13T01:15:10.457
FavoriteCount
0
LastActivityDate
2009-05-13T01:15:10.457
LastEditDate
LastEditorUserId
0
OwnerUserId
36103
ParentId
855441
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
Ordinarily, when you declare an object as <code>id</code> it counts an an "any" object (meaning that Objective-C will let you invoke any method from any class or protocol on the <code>id</code> without warning). However, when you declare an object as <code>id<SomeProtocol></code>, the meaning changes. In this case, you are instead saying: I will only invoke <code>SomeProtocol</code> methods on this object. The method: <pre><code>- (void)release; </code></pre> is declared in the <code>NSObject</code> protocol but you have explicitly stated: I will only invoke <code>MyProtocol</code> methods. So the compiler gives you a warning to tell you that you've broken your own promise. Therefore, instead of: <pre><code>id<MyProtocol> reference; </code></pre> you should actually declare: <pre><code>id<MyProtocol, NSObject> reference; </code></pre> or: <pre><code>NSObject<MyProtocol> reference; </code></pre> since <code>NSObject</code> (the class) implements <code>NSObject</code> (the protocol). or: <pre><code>id reference; </code></pre> which is the broadest of the lot: let me invoke anything on this object and never complain. You can also (as Barry Wark suggested) have <code>MyProtocol</code> include the <code>NSObject</code> protocol -- although from a design perspective, you normally only do this if implementing <code>MyProtocol</code> necessarily means using <code>NSObject</code>. Normally, we only do this if <code>NSObject</code> and <code>MyProtocol</code> are linked heritarily or semantically. <hr> A little information about the <code>NSObject</code> protocol: Everything you invoke retain/release/autorelease upon must implement this protocol. As you can infer from this: basically everything implements the <code>NSObject</code> protocol (even though a few things don't descend from the <code>NSObject</code> base class). Another quick clarification: <code>NSObject</code> (the class) and <code>NSObject</code> (the protocol) are not reimplementations of the same API. They are split as follows: <ul> <li>NSObject (protocol) implements everything required to handle/inspect an existing object in a generic sense (retain/release, isEqual, class, respondsToSelector: etc).</li> <li>NSObject (class) implements less generic methods: construction/destruction, thread integration, scripting integration.</li> </ul> So in most senses, the protocol is the more important of the two. Remeber that the class includes the protocol so if you descend from NSObject, you get both.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIn objective-C (iphone), how do I manage the memory of '@protocol' references?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMatt Gallagher
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. 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
 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.