Re: primitiveValueForKey Memory Management
Re: primitiveValueForKey Memory Management
- Subject: Re: primitiveValueForKey Memory Management
- From: mmalcolm crawford <email@hidden>
- Date: Mon, 30 May 2005 02:48:08 -0700
On May 30, 2005, at 2:41 AM, Phil Larson wrote:
On May 29, 2005, at 11:27 AM, Chris Hanson wrote:
One thing to note about NSOutlineView is that it does not retain
the items passed to it by its datasource. Its datasource must own
the items.
Alright, so it seems that the NSManagedObject subclasses that are
returned from an NSFetchRequest are autoreleased. How are these
supposed to be handled?
Umm, just as you would any other autoreleased objects...
Say we want to display a list of Foo objects without using bindings
and using CoreData. So we execute a fetch request for all Foo
items. Are we supposed to retain these and hold these
Yes, just as you would any other objects.
and somehow detect when we should rerun the fetch request?
Yes, just as you would have to keep your collection updated using
almost any other application architecture.
Is CoreData meant to be used without bindings?
It may be used with or without bindings -- the two tutorials provided
in the documentation illustrate both situations.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden