Thanks, that solved it.
Olivier
http://www.flickr.com/photos/otusweb/
On Tue, Apr 20, 2010 at 4:16 PM, Keary Suska wrote:
> On Apr 20, 2010, at 11:22 AM, olivier destrebecq wrote:
>
> > Just to clarify, when i say save, i mean call save: on the context and
> write
> > it to disk. Which the do
On Apr 20, 2010, at 11:22 AM, olivier destrebecq wrote:
> Just to clarify, when i say save, i mean call save: on the context and write
> it to disk. Which the documentation state that you don't have to call save:
> to be able to query for objects and that modified object will be found.
Yes. Ever
Just to clarify, when i say save, i mean call save: on the context and write
it to disk. Which the documentation state that you don't have to call save:
to be able to query for objects and that modified object will be found.
If i wait a little bit (probably for the next event in the event loop) t
Hi Olivier
> I create an object and insert it into the context, then i update a couple
> properties.
>
> Later I i do a fetch request with a predicate on the property i updated
> after the insertion. If i do this fetch right after the update of the
> property (using the accessors provided by core
I create an object and insert it into the context, then i update a couple
properties.
Later I i do a fetch request with a predicate on the property i updated
after the insertion. If i do this fetch right after the update of the
property (using the accessors provided by coreData), then the fetch do
