On Thu, 1 Jul 2010 15:38:35 -0700, Jerry Krinock said: >I'm debugging a problem with Save As in a Core Data document, and I'm >not sure if the following is part of the main show, or a sideshow. > >A document contains only one object in a given entity. I've written a >little debugger method which simply fetches all objects of a given >entity and logs the result. [1] > >Before my Save As operation, running this method logs an array of one >object, as expected. But after the Save As, it logs an empty array >(empty fetch). But wait, if I then change an attribute of the "missing" >object, using the app's GUI, and re-run this logging method, the object >reappears in the new fetch result. And it has the same pointer address >and permanent objectID as before. And its -isFault and -isDeleted are >both NO, both before and after its dis/reappearance. > >Is there any Core Data behavior that might explain this?
Since no one else has replied.... I can only say that this rings some vague bells. What OS? I've seen weirdo Core Data bugs with Save As, but they are all fixed as of 10.6.4, with the exception of this one: Steps to Reproduce: - open Xcode - create NSPersistentDocument-based project - build and debug - File > Save As - try to save in /System/Library - it fails, and gives a nice error message - now, try to save on your desktop Expected Results: - success Actual Results: - an exception is thrown: -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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
