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 use an EO's Constructor.Don't set EO properties in the EO constructor - use
From Apple's Documentation:
You may wonder why it's not recommended to initialize an enterprise object's values in an object's constructor. An enterprise object's constructor represents the earliest state in the life of a particular object. The state of an enterprise object at the point of construction is not complete; the object is not fully initialized. It may not yet have been inserted into an editing context and it might not even have been assigned a global ID. You don't ever want to manipulate an enterprise object that isn't in an editing context or that doesn't have a global ID.
Therefore, any logic you add in an enterprise object's constructor may fail or be invalidated while the object finishes initializing. By providing custom logic in awakeFromInsertion or awakeFromFetch, however, you are guaranteed that an enterprise object is fully initialized.
awakeFromInsertion(...)there are two times that this method can be called when the EO being inserted is not actually being initialized for the first time.
- If it's being reinserted to a EC after it was deleted from another or the same EC. Only new EOs will have a temporary GlobalID.
- If it's being saved to the server-side application by a Java Client WebObjects application. These EOs will have been inserted on the client-side and likely already have values set. To avoid overriding these values, you should verify that the attribute's value is null first.
Don't change the value of an attribute or behavior of a relationship in its accessor methodEOF 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. Don't:
- Don't provide default values - Do use
- Don't sort a to-many relationship's values - Do write a convenience method like
- Don't format a String or Date or Number attribute - Do formatting in helper classes or in the Component
- Don't change an attribute's data type
- Don't change an attribute's value when reading a different attribute. For example: Don't call
setFullName(...)when you call
- Don't provide default values - Do use
Always Insert First.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 inDoing this in
validateValueForKey(...)is ok as Chuck Hill noted in the list.
Always invokeIf overriding
superwhen overriding EOF methods
awakeFromInsertion(...), remember to call the superclass implementation. Same with
Don't use EOF in model class static initializersDoing so forces EOF into operational mode before the frameworks are initialized. Use lazy loading of the entity instead.
Don't use mutable classes as attributesAttributes of (
NSMutableDictionaryor any other class that can change internal state after creation) will confuse EOF. If you want this effect, use immutable classes and provide cover methods to replace the immutable instance with an updated instance. For example:
Always Lock your EditingContextDon't call any EOEditingContext methods, or any methods on an EO in an EOEditingContext without first ensuring that the EOEditingContext is locked. That includes bindings in a WOD. It's your job to make sure the EO's that you bind to in a page are locked.
Project Wonder provides auto-locking, so you don't have to worry about this.
Don't Expose Foreign Keys as Class AttributesDoing this will result in buggy unexpected behavior in EOF. Same goes for compound PKs (Primary Keys) where the compound PK values are set automatically by EOF (for example in a many-to-many join entity). However exposing compound PK attributes as class attributes is OK for an entity where you are manually setting the PK values yourself. Interestingly, even though it is not recommended, exposing a Primary Key as a class attribute will not break EOF.
Always use .imutableClone() when iterating over a to-many relationship with a for-each loop.It doesn't matter if you use the relationship directly or use a local variable that was populated by
getValueForKey("myRelatedObjects")you should always use an imutableClone of the array, otherwise you will likely just have a pointer to the actual relationship, which can easily change.