On Wed, 30 Mar 2011 15:57:53 -0700, Quincey Morris said:
That FAQ is actually pretty darn close to my original question really.
But it's a little vague. I've never been clear on when/where it's safe
to use KVO from one managedobject to another. It says You must add and
remove the parent
On Mar 31, 2011, at 14:13, Sean McBride wrote:
Still, I'm hesitant to do KVO observation from one managedobject to
another. I currently don't do that anywhere. Do you use this technique
frequently?
Frequently? Yes. With Core Data? Not recently, but in the past, similar things.
It's
On Tue, 29 Mar 2011 18:15:28 -0700, Quincey Morris said:
On Mar 29, 2011, at 14:57, Sean McBride wrote:
I've considered adding a optional transient to-one relationship to
Department named 'employeeId0' and binding the tablecolumn to
departmentsArrayControllerarrangedObjectsemployeeId0name,
On Mar 30, 2011, at 15:02, Sean McBride wrote:
By 'normal derived property' do you mean in this sense:
http://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/
CoreData/Articles/cdFAQ.html#//apple_ref/doc/uid/TP40001802-SW3
That's the sense I meant.
That FAQ is actually
On 30 March 2011 17:02, Sean McBride s...@rogue-research.com wrote:
On Tue, 29 Mar 2011 18:15:28 -0700, Quincey Morris said:
On Mar 29, 2011, at 14:57, Sean McBride wrote:
I've considered adding a optional transient to-one relationship to
Department named 'employeeId0' and binding the
Hi all,
Consider a Core Data app, with Employee and Department entities. The
Employee entity has 'name' and 'number' attributes. Department has a to-
many relationship to Employees.
I need a tableview of departments, where one column should show the
'name' of the employee who's 'number' is 0.
