Maybe -unserializedRepresentation... should be a class method?

[ahti]

Just a quick thought: I just made the mistake to implement -unserializedRepresentation... in a way that relied on another database field being loaded already.

This mistake could be made impossible by changing the method to be a class method. Alternatively, a way to specify in which order database values are unserialized could be provided, although that could well be unnecessary complexity.

What I am worried about is people making the same mistake I did and having it work fine in development just by chance, and then having a change in e.g. how enumerateObjectsAndKeys... works screw up apps.