On Oct 31, 2009, at 12:25 PM, Richard Somers wrote:
On Oct 31, 2009, at 10:12 AM, Jim Correia wrote:
Typically you set up the baseline value in -awakeFromFetch.
Is there a specific reason you need this to be undoable?
When the managed object is removed, didTurnIntoFault is called and
the
On Oct 31, 2009, at 10:12 AM, Jim Correia wrote:
Typically you set up the baseline value in -awakeFromFetch.
Is there a specific reason you need this to be undoable?
When the managed object is removed, didTurnIntoFault is called and the
custom data caches are deleted. When the user does an
On Sat, Oct 31, 2009 at 12:05 PM, Richard Somers
wrote:
> The documentation states didTurnIntoFault "method may be used to clear out
> custom data caches". So far so good.
>
> I was creating custom data caches in awakeFromFetch (or awakeFromInsert)
> until I realized that awakeFromFetch does not
You can create a custom accessor and re-create the cache if it is not
present when the accessor is called.
On 2009-10-31, at 12:05 PM, Richard Somers wrote:
I have custom data caches associated with a managed object.
The documentation states didTurnIntoFault "method may be used to
clear ou
I have custom data caches associated with a managed object.
The documentation states didTurnIntoFault "method may be used to clear
out custom data caches". So far so good.
I was creating custom data caches in awakeFromFetch (or
awakeFromInsert) until I realized that awakeFromFetch does not
