StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAbout usage CoreData: relationships or id
primarykey
Id
17856151
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-25T10:59:40.437
FavoriteCount
0
LastActivityDate
2013-07-25T11:41:39.393
LastEditDate
2013-07-25T11:28:17.070
LastEditorUserId
2618361
OwnerUserId
2618361
ParentId
0
PostTypeId
1
Score
0
ViewCount
86
LastEditorDisplayName
text
Body
I have a quick question about appropriate usage of framework CoreData. Introduction: i have an application with a few UITableViewControllers offering different entities. 1 - list of events - entity "ResponseEventsItem"     every event had interrelated records:         - spakers (entity "ResponseEventsSpeakersItem") - every record has only one parent - ResponseEventsItem         - locations (entity "ResponseEventsSpeakersItem") - every record has only one parent - ResponseEventsItem         - schedule (entity "ResponseEventsSpeakersItem") - every record has only one parent - ResponseEventsItem, and also other related records: ResponseSpeakersItem and/or ResponseLocationsItem          - sponsors (entity "ResponseEventsSponsorsItem") - every record has only one parent - ResponseEventsItem 2 - about the town (entity "ResponseCityAboutItem") 3 - attractions (entity "ResponseSightsItem") 4 - hotels (entity "ResponseHotelsItem") - can be related to ResponseBonusesItem 5 - fastfood (entity "ResponseFoodsItem") - can be related to ResponseBonusesItem 6 - entertainment (entity "ResponseEntertainmentsItem") - can be related to ResponseBonusesItem 7 - special offers (entity "ResponseBonusesItem") - this record is related to "ResponseEventsItem" and ("ResponseHotelsItem" or "ResponseFoodsItem") QUESTION: what is the best way to use framework CoreData? 1 - create a single storage (store NSPersistentStore) and load up everything into it and establish connections based on relationship of cores (for instance, relationships to-many ResponseEventsItem.locations -> [ResponseLocationsItem] ) or 2 - or to create an individual storage of each separate core ( however in this particular case we will not be able to use relationships because relationships exist only within one given storage) and to make sure that selection of interrelated data is done through ID, like in a regular SQL data base (mysql as an example). When I am asking what is the best way, I actually mean what is the most efficient and most common way (quickest response time)? is there a chance that the storage will overload in case if all the data will be located in only one storage?
Tags
<ios><core-data>
Title
About usage CoreData: relationships or id
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USIlya Lyaschenko
UserOwnerUserId
1. USIlya Lyaschenko
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.