#6 ✓resolved
mklaurence (at gmail)

Relationship deserialization is brittle (and only works for bidirectional relationships)

Reported by mklaurence (at gmail) | March 6th, 2010 @ 04:59 PM | in Beta release (0.9)

Relationship deserialization currently looks at the reverse relationship and attempts to assign there, which is probably the wrong approach (it was easier at the time, though!)

We should probably just use the regular (not inverse) setter for toOnes. For toManys, we can look for addObject: methods and use those if they exist; otherwise we can use more esoteric processing (like using the inverse setter if it's a one-many, and who knows what if it's a many-many...)

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Local & remote resource management library for Objective-C using Core Data with Rails-like syntax. WARNING: The API is currently under heavy development and will undoubtedly change.

Shared Ticket Bins

People watching this ticket