StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8514458
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-15T02:39:34.970
FavoriteCount
0
LastActivityDate
2011-12-15T02:49:20.190
LastEditDate
2011-12-15T02:49:20.190
LastEditorUserId
1023019
OwnerUserId
1023019
ParentId
8512551
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
You mean the return value from that method? <pre><code>+ (ContactInfo *)findOrCreateContact:(NSDictionary *)data inManagedObjectContext:(NSManagedObjectContext *)context </code></pre> First the naming of the function state <code>find OR create</code> so with a name like that you should return an object in both case, the one you have find or the one just created. That would avoid possible confusion. Second, Your return type is an object, so you should return <code>nil</code> or an object. So at this point you have to decide if you want to comply with your naming or not, but let say you want. You could have a method like this : <pre><code>+ (ContactInfo *)findOrCreateContact:(NSDictionary *)data inManagedObjectContext:(NSManagedObjectContext *)context contactWasCreated:(BOOL *)isNew </code></pre> By passing a pointer to a BOOL you can get set it to YES if the ContactInfo was created and NO if you are returning an one that already existed, and you can still return nil if you wasn't able to have a ContactInfo to return. Passing a BOOL as a pointer is inspired by <code>- (BOOL)save:(NSError **)error</code> where you are passing a pointer to an object an can retreive the NSError if needed. So in your if you could say <pre><code>if (contanctInfo && wasCreated) { // I've got a new one } else if (contactInfo) { // I just receive an old one } else { // something very bad just happened... } </code></pre> You could also decide to return a NSDictionary with the ContactInfo as one entry and a NSNumber for the BOOL as an other entry.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCore Data - Inserting new object, check if the same objects exists, handle return
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVincent Bernier
UserOwnerUserId
1. USVincent Bernier
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCore Data - Inserting new object, check if the same objects exists, handle return
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThat did it, thanks! :)
 singulars
 PostPostId
 PO
 UserUserId
 USflashfabrixx

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.