Databases
StackOverflow2013
Postsdbo
PONSManagedObject Entity Inheritance causes NSInternalInconsistencyException
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONSManagedObject Entity Inheritance causes NSInternalInconsistencyException
    primarykey
    data
    text
    <p>I have an NSManagedObject ElementA with several attributes that should exist in ElementB through a parent-child relationship. When setting ElementA as the Parent Entity to ElementB, the NSPersistentStoreCoordinator fails. The ManagedObjectModel is correctly being built, and the entities/classes work separate of each other. The only difference between the app failing and compiling is this parent-child relationship. None of the attributes from either entity overlap.</p> <p>I don't have enough rep yet, so the images are at the following links: <a href="http://i.stack.imgur.com/XZdhs.png" rel="nofollow">ElementA Model</a>, <a href="http://i.stack.imgur.com/fLVZg.png" rel="nofollow">ElementB Model</a>.</p> <p>As far as troubleshooting goes, I've tried all of the following:</p> <ol> <li>With and without implementing custom classes.</li> <li>Setting ElementA as abstract (however I need it to not be abstract)</li> <li>Removing and then adding in the attributes one at a time (including emptying all attributes of both entities)</li> <li>Resetting Xcode (clean), the simulator (reset all), and restarting my machine.</li> </ol> <p>I've read up on Apple's Docs (Core Data Programming Guide: Managed Object Models) and everything seems to align with their guidelines for Entity Inheritance.</p> <p>This is the line that fails:</p> <pre><code>__persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]]; </code></pre> <p>What do I seem to be missing here? It's got to be obvious as this does not seem like it should be this hard. Any and all help is appreciated!</p> <p><strong>Edit for @Rog's Comment</strong></p> <p>The application fails as soon as the core data model is accessed for the first time at startup. The new images above show that I am trying to set the Parent Entity of ElementB using the Model Editor. The following is the error message I'm receiving:</p> <pre><code>uncaught exception 'NSInternalInconsistencyException', reason: 'Bad model. For entity 'ElementA' subentity 'ElementB (0x785d790)' is not registered in NSManagedModelModel. Model has a reference to ElementB (0x785e320)' </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USsbonami
    1. USsbonami
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONSManagedObject Entity Inheritance causes NSInternalInconsistencyException
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONSManagedObject Entity Inheritance causes NSInternalInconsistencyException
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou need to provide more details. Post a screenshot of your managed object model view. Also when is it crashing - during start up, when instantiating one of the managed objects. How are you setting ElementA as parent / superclass of ElementB? What is the error that you are getting?
      singulars
      1. PONSManagedObject Entity Inheritance causes NSInternalInconsistencyException
      1. USRog
 

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