small medium large xlarge

Back to: All Forums  Core Data
Generic-user-small
24 Apr 2010, 16:27
Michael Taft (2 posts)

How do you (M. Zarra) recommend designating an entity as a default entity that must persist across time? (i.e. the entity that the app uses when it launches each time) The two obvious possibilities are using a URI string in a plist, or actually having an isDefault boolean in the entity itself.

Do you recommend one of these approaches over the other? Is there a third, better approach I’m not thinking of? Are there any hidden gotchas to look out for?

Currently, I’m using the URI-in-plist approach, but I’m thinking the boolean as an attribute might work better. Any thoughts?

Thanks.

Avatarsmall_pragsmall
24 Apr 2010, 18:06
Marcus S. Zarra (284 posts)

I would recommend the Boolean approach because the objectID can and does changer during versioning. Unfortunately there is not really a good third option at this time.

You must be logged in to comment