StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2855879
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-05-18T09:18:59.837
FavoriteCount
0
LastActivityDate
2010-05-18T09:18:59.837
LastEditDate
LastEditorUserId
0
OwnerUserId
151019
ParentId
2855609
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I think you need to start looking at Objective C from the start again it is not C++ Your code example does not tell us that modelClass is a LectureModel so there are things missing so I might have misunderstood some things. First you have to call [super init] directly see <a href="http://developer.apple.com/mac/library/referencelibrary/GettingStarted/Learning_Objective-C_A_Primer/index.html#//apple_ref/doc/uid/TP40007594Blockquote" rel="nofollow noreferrer">Apple Objective C Primer</a>. In Objective C you use composition instead than inheritance more often than in C++ - In this example I would use delegation to allow use of dictionary. LectureModel will pass any messages it does not understand to the dictionary attribute. Also from <a href="http://developer.apple.com/mac/library/documentation/Cocoa/Reference/Foundation/Classes/NSDictionary_Class/Reference/Reference.html#//apple_ref/occ/cl/NSDictionary" rel="nofollow noreferrer">NSDictionary</a> NSDictionary and NSMutableDictionary are part of a class cluster, so the objects you create with this interface are not actual instances of the these two classes. Rather, the instances belong to one of their private subclasses. So NSMutableDictionary is not really a good class to extend. This is partial code there are many parts missing including dealloc <pre><code>@interface LectureModel : NSObject { NSMutableDictionary *dict; } ... @end @implementation LectureModel -(LectureModel*)init { if (self = [super init]) { dict = [[NSMutableDictionary dictionary]retain]; // need to keep this } return self; } - (void)forwardInvocation:(NSInvocation *)invocation // See NSObject for details { SEL aSelector = [invocation selector]; [invocation invokeWithTarget:dict]; // let dict do the work } ... @end </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POObjC: Alloc instance of Class and performing selectors on it leads to __CFRequireConcreteImplementation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMark
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POObjC: Alloc instance of Class and performing selectors on it leads to __CFRequireConcreteImplementation
 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. COThank you, that was quite insightful! I will try it your way.
 singulars
 PostPostId
 PO
 UserUserId
 USArakyd

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.