Re: CoreData entity mutability
Re: CoreData entity mutability
- Subject: Re: CoreData entity mutability
- From: Antoine Maillard <email@hidden>
- Date: Tue, 20 Jan 2009 16:13:11 +0100
Thanks guys, I finally chose to duplicate the object.But I think that would
be a pretty cool feature to be able to "mutate" an object.
For instance, if you have an ancestor A which has a small set of properties
and which evolves to a more sofisticated object (a descendant), there is no
use copying it, it's an evolution, not a creation...
--Antoine
On Tue, Jan 20, 2009 at 1:27 PM, Antoine Maillard <
email@hidden> wrote:
> Thanks guys, I finally chose to duplicate the object.But I think that
> would be a pretty cool feature to be able to "mutate" an object.
> For instance, if you have an ancestor A which has a small set of properties
> and which evolves to a more sofisticated object (a descendant), there is no
> use copying it, it's an evolution, not a creation...
>
> --Antoine
>
> On Tue, Jan 20, 2009 at 3:42 AM, Kyle Sluder <email@hidden>wrote:
>
>> On Mon, Jan 19, 2009 at 8:39 AM, Antoine Maillard
>> <email@hidden> wrote:
>> > How can I convert a NSManagedObject of type A into type B ?
>>
>> How often do you do this in regular code? Is it common for a method
>> to change the identity of the receiver before returning? Hopefully
>> the answer is no (KVO trickery aside ;) ).
>>
>> Just remove the object and replace it with an managed object of entity B.
>>
>> --Kyle Sluder
>>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden