I hope that by "corrupt data" in the case of a many-to-many
relationship, you mean that if one isn't careful they may end up with
a row that links a foreign key from one table to a non-existent key in
another.
I mean no inverse relationships never have a join table, so trying to
pretend it's a
Sorry if this ends up showing twice, but the original message has been
moderator-queued for length since early this morning. Being several
steps behind in even *asking* Core Data questions has been frustrating
me all day, as I try to press on in no less ignorance than yesterday.
On Dec 11,
Consultant.interestingEmployees -- to-many relationship does not
have an inverse: this is an advanced setting (no object can be in
multiple destinations for a specific relationship)
This error doesn't make sense to me. Is it trying to say an object
can only "belong" to one to-many relationship?
On Dec 10, 2008, at 22:36, Nathan Vander Wilt wrote:
I'm trying to port my model code to use Core Data. My model is
something like this:
I have a Company. It has two to-many relationships, currentEmployees
and previousEmployees which are naturally both to Employees.
Employees have a to-on
I'm trying to port my model code to use Core Data. My model is
something like this:
I have a Company. It has two to-many relationships, currentEmployees
and previousEmployees which are naturally both to Employees.
Employees have a to-one relationship to the Company that is the
inverse of
