Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So you've created the mapping for each NSManagedObject (and they work), but now you want to establish a relationship between "Category" and "Elements".</p> <p>The problem is that there isn't an information for the mapping of Elements in which Category each element belongs (the unique key is missing). So you need to add the <code>cat_id</code> to the Elements JSON to ensure that this keypath is available.</p> <pre><code>// Elements JSON [ { "cat_id": "1313", "art_id": "1", "node": { "author": "name" }, "small_url": 0 }, ... ] // Edit keypath in relationship mapping [elementsMapping addPropertyMapping:[RKRelationshipMapping relationshipMappingFromKeyPath:@"cat_id" toKeyPath:@"category" withMapping:categoryMapping]]; </code></pre> <p>In addition you could use the following to methods to track if the mapping works. </p> <pre><code>1) -com.apple.CoreData.SQLDebug 1 // Add in "Arguments" Tab &gt; "Arguments Passed On Launch" 2) RKLogConfigureByName("RestKit/*", RKLogLevelTrace); // Add to AppDelegate` </code></pre> <h2>Edit</h2> <h3>Mapping</h3> <p>Did you update the entity <code>Elements</code> in your Data Model and your NSManagedObject with the given value? Seems like you didn't.</p> <pre><code>@interface Elements : NSManagedObject @property (nonatomic, retain) NSNumber * catId; @property (nonatomic, retain) NSNumber * artId; @property (nonatomic, retain) NSString * author; @property (nonatomic, retain) NSString * title; @property (nonatomic, retain) NSManagedObject *category; @end </code></pre> <h3>Routing</h3> <p>The path your using for your get request won't work because <code>@"/detailaddress/:catId"</code> isn't a valid path. You can on the one hand set the routing of the object manager in general or define a response description.</p> <pre><code> // Route for get operation [[RKObjectManager sharedManager].router.routeSet addRoute:[RKRoute routeWithClass:[Category class] pathPattern:@"/detailaddress/:catId" method:RKRequestMethodGET]]; // Response descriptor taken from the Core Data same application RKResponseDescriptor *responseDescriptor = [RKResponseDescriptor responseDescriptorWithMapping:categoryMapping pathPattern:@"/detailaddress/:catId" keyPath:nil statusCodes:RKStatusCodeIndexSetForClass(RKStatusCodeClassSuccessful)]; [objectManager addResponseDescriptor:responseDescriptor]; // Use general path for get request [[RKObjectManager sharedManager] getObjectsAtPath:@"/detailaddress" ... </code></pre> <p>But please check if the mapping and data model is set like expected first.</p>
    singulars
    1. This table or related slice is empty.
    1. PORestKit and saving to CoreData as NSManagedObject
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USflashfabrixx
    1. USflashfabrixx
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy i should do add this extra field? I dont really like it. I'm pretty sure i should use routing to do that but don't know excatly how.
      singulars
      1. PO
      1. USKuba
    2. COHow should the mapping know which object (given by the cat_id) should be the parent of the child your inserting? To verify my answer have a look at the wiki (paragraph "Relationships") https://github.com/RestKit/RestKit/wiki/Object-Mapping
      singulars
      1. PO
      1. USflashfabrixx
    3. COBecouse i pass arg in link. :catId that's why i think about routing.
      singulars
      1. PO
      1. USKuba
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload