Re: Core Data memory not freed after reset

2009-09-22 Thread Sean McBride
On 9/22/09 1:59 PM, Ben Trumbull said: >>> If you're using an NSArrayController in Entity mode, you can turn on >>> Use Lazy Fetching. You'll want to disable auto-rearrange content. >> >> Ben, >> >> May I ask, why turn off 'auto-rearrange content'? Is it not >> compatible >> with 'use lazy fetch

Re: Core Data memory not freed after reset

2009-09-22 Thread Ben Trumbull
On Sep 22, 2009, at 8:54 AM, Sean McBride wrote: On 9/21/09 4:21 PM, Ben Trumbull said: If you're using an NSArrayController in Entity mode, you can turn on Use Lazy Fetching. You'll want to disable auto-rearrange content. Ben, May I ask, why turn off 'auto-rearrange content'? Is it not

Re: Core Data memory not freed after reset

2009-09-22 Thread Sean McBride
On 9/21/09 4:21 PM, Ben Trumbull said: >If you're using an NSArrayController in Entity mode, you can turn on >Use Lazy Fetching. You'll want to disable auto-rearrange content. Ben, May I ask, why turn off 'auto-rearrange content'? Is it not compatible with 'use lazy fetching'? Or does 'auto-r

Re: Core Data memory not freed after reset

2009-09-21 Thread Ben Trumbull
Core Data has (or, I should say, had, since I haven't investigated the behavior in Snow Leopard) its own internal in-memory cache of object and attribute data, which means that, up to a point, data from a persistent store is in memory twice. AFAICT there's no way of unloading or controlling this c

re: Core Data memory not freed after reset

2009-09-21 Thread Ben Trumbull
in my SQLite backed Core Data app, a search action fetches from a large number of objects (>1.000.000) only to show them in a table. When the user exits search mode (search string empty), I'd like to free the managed objects to restore the app's normal memory footprint. I do that by resetting the

Re: Core Data memory not freed after reset

2009-09-21 Thread Quincey Morris
On Sep 21, 2009, at 05:40, Sebastian Morsch wrote: in my SQLite backed Core Data app, a search action fetches from a large number of objects (>1.000.000) only to show them in a table. When the user exits search mode (search string empty), I'd like to free the managed objects to restore the

Core Data memory not freed after reset

2009-09-21 Thread Sebastian Morsch
Hi, in my SQLite backed Core Data app, a search action fetches from a large number of objects (>1.000.000) only to show them in a table. When the user exits search mode (search string empty), I'd like to free the managed objects to restore the app's normal memory footprint. I do that by r