On 11/2/09 1:38 PM, Ben Trumbull said:
The only caveat is you cannot change relationships from within -
awakeFromFetch. This is documented:
This is something I know and avoid, but it turns out this is what's
happening afterall! Thanks!
Is there some way to catch such violations? I
On 10/29/09 5:23 PM, Ben Trumbull said:
Even if I do [scene addTargetsWeak:[scene targetsWeak]] I get the error.
Does this make any sense to anyone?
The only caveat is you cannot change relationships from within -
awakeFromFetch. This is documented:
Ben,
This is something I know
On 10/22/09 4:59 PM, Melissa J. Turner said:
I have an entity 'Scene' with a to-many relationship to an entity
'Target'. The inverse relationship is also to-many. Both relationships
are optional and the delete rule for both sides is nullify.
To repro, I delete all Scenes then try to save.
On Oct 29, 2009, at 16:55 , Sean McBride wrote:
On 10/22/09 4:59 PM, Melissa J. Turner said:
I have an entity 'Scene' with a to-many relationship to an entity
'Target'. The inverse relationship is also to-many. Both relationships
are optional and the delete rule for both sides is
Hi all,
Core Data is giving me a validation error when I try to save a document
after making a simple change.
I have an entity 'Scene' with a to-many relationship to an entity
'Target'. The inverse relationship is also to-many. Both relationships
are optional and the delete rule for both sides
On Oct 22, 2009, at 16:26, Sean McBride wrote:
Hi all,
Core Data is giving me a validation error when I try to save a document
after making a simple change.
I have an entity 'Scene' with a to-many relationship to an entity
'Target'. The inverse relationship is also to-many. Both
Core Data is giving me a validation error when I try to save a document
after making a simple change.
I have an entity 'Scene' with a to-many relationship to an entity
'Target'. The inverse relationship is also to-many. Both relationships
are optional and the delete rule for both sides is
