Thanks for the explanation, I like when you have to bend the rules ;)
Aurélien,
Objective Decision Team
On 29 mai 09, at 23:25, Ben Trumbull wrote:
On May 29, 2009, at 2:49 AM, Aurélien Hugelé wrote:
Core Data multithreading basic rule is to avoid passing managed
objects across threads
On 5/29/09 2:25 PM, Ben Trumbull said:
>You can download the debug version of Core Data from ADC and use the
>multithreading assertions.
Not if you're using 10.5.7 you can't. :( The 'Debug and Profile
Libraries' for 10.5.7 are still unavailable.
--
_
On May 29, 2009, at 3:40 PM, Kyle Sluder wrote:
And if it's determined to already be clear enough, please close the
bug
No, there is something there to be addressed -- thanks for the
clarification.
mmalc
___
Cocoa-dev mailing list (Cocoa-d
On Fri, May 29, 2009 at 2:59 PM, mmalc Crawford wrote:
> Could you elaborate on what is unclear?
Perhaps it would suffice to just have a simple one-liner that mentions
NSManagedObjectContextDidSave, specifically in the context of
multi-threaded Core Data. It's not an easy topic, so I think an
ai
On May 29, 2009, at 2:46 PM, Kyle Sluder wrote:
Can we please have some further clarification on this in the docs
please? r.6933634
The documentation states explicitly:
You can use this method to, for example, update a managed object
context on the main thread with work completed in anoth
On Fri, May 29, 2009 at 2:25 PM, Ben Trumbull wrote:
> In a literal sense, it can appear that way. The specific implementation
> details of mergeChangesFromContextDidSaveNotification address the paradox.
> The framework gets to bend its own rules a touch in much the same way that
> an object acc
On May 29, 2009, at 2:49 AM, Aurélien Hugelé wrote:
Core Data multithreading basic rule is to avoid passing managed
objects across threads, and pass objectIDs instead.
yup.
To "synchronize" 2 mocs from 2 different threads (sharing the same
psc), I use mergeChangesFromContextDidSaveNotific
Hi !
I'm having strange crashes in my threaded core data application. Happy
WWDC is in few days!
Core Data multithreading basic rule is to avoid passing managed
objects across threads, and pass objectIDs instead.
To "synchronize" 2 mocs from 2 different threads (sharing the same
psc), I
