Some things to avoid when working with EOF. Some of these things are contraindicated in Apple documentation, others are not. But all are things that experience shows EOF does not expect, and can lead to all sorts of trouble, including mysterious exceptions, and EOF getting confused about what changes must be saved to the database.
- Don't set EO properties in the EO constructor - use
Note: When overriding
awakeFromInsertion(...), it's important to check that the EO isn't being reinserted to the EC after it was deleted. For example:
- Don't do anything to an EO before inserting it into an editing context. Always insert EOs into ECs immediately. See rule #1.
- Don't modify any EO properties in
validateFor...(...)methods. Doing this in
validateValueForKey(...)is ok as Chuck Hill noted in the list.
- If overriding
awakeFromInsertion(...), remember to call the superclass implementation. Same with
- Don't change the behavior of methods that EOF uses. For example, do not override to-many relationships to return a sorted list of the related objects. Make another method to do this.
- Don't use EOF in model class static initializers. Doing so forces EOF into operational mode before the frameworks are initialized. Use lazy loading of the entity instead.
- Don't use mutable classes (
NSMutableDictionary, or any other class that can change internal state after creation) as attributes. If you want this effect, use immutable classes and provide cover methods to replace the immutable instance with an updated instance. You and EOF will be much, much, much happier. For example:
- Don't change the value of an attribute in the accessor method! EOF calls those accessor methods many times over the life of the EO. An accessor method is the last place that you want to be making any changes or doing any computations to determine the value. Default values should be set in
awakeFromInsertion(...). If you need to update one attribute (i.e. lastChangedDate) when another attribute (i.e. userName) is changed then implement the
setUserName()method and document that it has the side effect of calling
setLastChangedDate(...). An alternate method if you would need to implement too many set methods or if you're concerned about overhead of calling
setLastChangedDate()too many times is to implement a listener for the editingContextWillSaveChanges notification from the EOEditingContext and call