Quincey: I am a bit in a hurry, so I will answer quickly:
> I think maybe you have more design options here. For example, you can [in > principle, I think] multithread with a single MOC without locks if you pass > "ownership" of the MOC around between threads that make changes, so that > ownership serializes access. That requires the ownership passing to be thread > safe, and you already have [I think] the What do you mean exactly? Could you elaborate just a little bit? > Finally, when struggling with Core Data like this, it's worthwhile to > repeatedly ask yourself if Core Data is the correct technology to use. Just > because a solution to your application's problem can be describe in > functional Core Data terms, that doesn't necessarily mean that Core Data is > the best (or even a good) actual solution. Well, since I may deal with sets of more than 100,000 entities, Core Data is appealing because of its embedded SQLite code. Fetching through CD is certainly way faster than the blind solution which would involve enumerate each candidate at each operation… > FWIW, which may not be much. I *very much* appreciate your help and the time you take to answer. Cheers! Vincent_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
