Note that there are some explanatory texts on larger screens.

plurals
  1. USFerdev
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COI've changed the `entityA.products = orderedSet` to `entityA.setProducts(orderedSet)` and that has fixed the first bottleneck, apparently. The save action still takes ages, though. Looks like hardware limitation, as you said earlier, since in the simulator it only takes 0.2 secs to save the context, while in the iPhone is taking around 4-6 seconds for the very same data.
      singulars
    2. COI'll try to explain myself better. The fetch is ordered (descently) using a numeric property of entity b. Once the fetch is made, all records are ordered using that field. Hence, I need an ordered relationship to be able to mantain that order. Anyway, I've just tried disabling the order attribute in the relationship, and the performance is more or less the same. I guess I'm doing something terribly wrong which is causing my performance problems. Thanks again!
      singulars
    3. COThanks Andrew for your response. Answering your questions: 1. Yeah, indexing a relationship probably doesn't make any sense, so I'll remove it. But, I do need the ordered relationship. The order of the B records are important.... Is there any other way to do this using CoreData? 2. No, because I can't assing an ordered set to a bulk setter. I don't know if this is a mistake I'm making, or if it's a known issue. I confess I haven't read further info about this. 3. Yeah, all b records are previously fetched... 4. Does this rule remove also the b records? Or just the relationship info?
      singulars
 

Querying!

 
Guidance

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