On Jul 19, 2010, at 5:47 PM, Quincey Morris wrote: > AFAICT, this is telling me that Core Data has itself cached the NSData object > in a "row cache". That's very bad news, because it seems to persist in there > indefinitely, until the managed object context is finally disposed of (which > I can't do in the middle of the import).
Why not? Managed object contexts are very cheap to create, so implementing a create-save-destroy loop shouldn't have a negative impact. But if you need some other data to "persist" in the context throughout the import process unchanged, that would be an issue, but may be solved by factoring it out to its own MOC. > Does anyone know of a way to empty or disable the row cache, or can anyone > provide a better insight into what's going wrong? Barring the issue I mention above, have you tried calling -reset on the context? If anything, I would expect it to purge caches, but there's nothing to back that up... HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ 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
