On Nov 27, 2011, at 9:23 PM, Quincey Morris
wrote:
> On Nov 27, 2011, at 20:50 , Tom Harrington wrote:
>
>> If they're different objects then I'm getting duplicates, which is at
>> least as much of a bug and possibly more so. What I observe is that if
>> I add 10 objects, I get 20 calls to awak
On Nov 27, 2011, at 20:50 , Tom Harrington wrote:
> If they're different objects then I'm getting duplicates, which is at
> least as much of a bug and possibly more so. What I observe is that if
> I add 10 objects, I get 20 calls to awakeFromInsert, 10 for the child
> context and 10 for the parent
On Sun, Nov 27, 2011 at 6:09 PM, Quincey Morris
wrote:
> On Nov 27, 2011, at 16:49 , Tom Harrington wrote:
>
> Actually I don't, so far as I can tell. As I mentioned in my previous
> message, I get the same managed object ID both times. I haven't
> checked the address, but surely if they were diff
On Nov 27, 2011, at 16:49 , Tom Harrington wrote:
> Actually I don't, so far as I can tell. As I mentioned in my previous
> message, I get the same managed object ID both times. I haven't
> checked the address, but surely if they were different objects they
> wouldn't have the same ID.
You're wro
On Sun, Nov 20, 2011 at 2:34 PM, Richard Somers
wrote:
> On Nov 16, 2011, at 6:16 PM, Tom Harrington wrote:
>
>> I'm finding that if I use nested managed object contexts,
>> awakeFromInsert will be called twice on new objects.
>
>
> On Mac OS X 10.7 NSManagedObjectContext can have a parentContext.
On Sat, Nov 19, 2011 at 6:49 PM, Roland King wrote:
>
> On Nov 20, 2011, at 5:48 AM, Jerry Krinock wrote:
>
>>
>> On 2011 Nov 16, at 17:16, Tom Harrington wrote:
>>
>>> I'm finding that if I use nested managed object contexts,
>>> awakeFromInsert will be called twice on new objects.
>>
>>> I'm won
On Nov 16, 2011, at 6:16 PM, Tom Harrington wrote:
> I'm finding that if I use nested managed object contexts,
> awakeFromInsert will be called twice on new objects.
On Mac OS X 10.7 NSManagedObjectContext can have a parentContext.
Perhaps this would be applicable.
--Richard
_
On Nov 20, 2011, at 5:48 AM, Jerry Krinock wrote:
>
> On 2011 Nov 16, at 17:16, Tom Harrington wrote:
>
>> I'm finding that if I use nested managed object contexts,
>> awakeFromInsert will be called twice on new objects.
>
>> I'm wondering if this is a Core Data bug or a documentation bug.
>
On 2011 Nov 16, at 17:16, Tom Harrington wrote:
> I'm finding that if I use nested managed object contexts,
> awakeFromInsert will be called twice on new objects.
> I'm wondering if this is a Core Data bug or a documentation bug.
I'd say it's a pretty serious Core Data bug. I've not had an occ
I'm finding that if I use nested managed object contexts,
awakeFromInsert will be called twice on new objects.
The first call to -awakeFromInsert happens when I actually create a
managed object and insert it into the child context. On this call, if
I break in awakeFromInsert, self's managed object
10 matches
Mail list logo