• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreData, reset a persistent store
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData, reset a persistent store


  • Subject: Re: CoreData, reset a persistent store
  • From: "Shawn Erickson" <email@hidden>
  • Date: Wed, 15 Nov 2006 16:15:56 -0800

On 11/15/06, Pierre Chatelier <email@hidden> wrote:
> That is the issue with the memory and the speed then.  Somehow
> those objects are becoming fully realized which is causing the
> memory spike and probably the delay as well.
I disagree ! The objects *are* faults (remember, no "Object is not
faulted" is displayed).

...confused...

Your code is the following...

    if (![object isFault]) {
        NSLog(@"Object is not faulted");
    }

Based on the if logic the log statement can be more clearly stated as "object data must be in memory". Review the documentation for -[NSManagedObject isFault].

You are seeing the log message so the object has been loaded into memory.

-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >CoreData, reset a persistent store (From: Pierre Chatelier <email@hidden>)

  • Prev by Date: [ANN] ANTLR 3.0 beta 5 release
  • Next by Date: Re: CoreData, reset a persistent store
  • Previous by thread: CoreData, reset a persistent store
  • Next by thread: Core data in Leopard
  • Index(es):
    • Date
    • Thread