On Apr 7, 2011, at 11:23, Chase Latta wrote: > Assuming that your users won't be changing their language that often > the overhead in translating the names would be very limited.
Functionally, what you suggest seems feasible, but because we're talking about iOS, I think there are other considerations: -- This means storing every name twice in the persistent store. That could significantly increase the size of the store. -- There's a potential data integrity problem, if one of the localized strings files changes, and out of date strings are present in the store for that language. -- When the language changes, every object (of the relevant class) must be fetched from the store and rewritten. This could have a memory footprint impact, and a performance impact, that's significantly worse than just fetching and sorting. (Keep in mind that Core Data has property value caches separate from property values, so there might be more going on than the developer can control.) -- Dirtying and/or saving the persistent store might have other undesirable side-effects on the rest of the application. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
