WebObjects EOF Using EOF Accumulation Attractive

 

    Here is a little archetype about how to accumulation back a agglomeration of EOFaults:

    without triggering the fault:

     EOEnterpriseObject aReferenceObject = (EOEnterpriseObject)someFaults.lastObject();

     EOAccessFaultHandler aFaultHandler = (EOAccessFaultHandler) EOFaultHandler.handlerForFault(aReferenceObject);

     EOEditingContext anEditingContext = aFaultHandler.editingContext();

     String anEntityName = aFaultHandler.globalID().entityName();

     EOEntity anEntity =

     EOModelGroup.defaultGroup().entityNamed( anEntityName );

     EOEnterpriseObject aFault = (EOEnterpriseObject) someFaults.objectAtIndex(index);

     EOKeyGlobalID aGlobalID = (EOKeyGlobalID) anEditingContext.globalIDForObject( aFault );

     NSDictionary aPrimaryKey = anEntity.primaryKeyForGlobalID( aGlobalID );

     EOQualifier aQualifier = anEntity.qualifierForPrimaryKey( aPrimaryKey );

     EOQualifier aQualifier = new EOOrQualifier( someQualifiers );

     EOFetchSpecification aFetchSpecification = new EOFetchSpecification( anEntityName, aQualifier, null);

     anEditingContext.objectsWithFetchSpecification?(aFetchSpecification?);

     // Preloading Relationships ===

    This adjustment can be acclimated to prefetch relationships in a accumulation instead of accepting them blaze one by one. This can be acclimated to accomplished tune accumulation attractive in cipher instead of accomplishing it in the model. Be accurate of how you use this method. It will force a back from the database even if the altar are already buried in the item store. Acclimated afield this can reduce, instead of increase, performance.

     accessible changeless abandoned preloadRelationship(NSArray sourceEOs, Cord relationshipName)

     assuredly

     }

     }