Hello Gideon,
in contrast to the warnings in Apple's documentation, using a custom subclass
of NSManagedObjectContext is fine and often necessary to enrich the context
information of your managed objects. We have successfully using this technique
for complex applications since the first version
Ah, excellent find, thanks. I inherited the code - will see if I can work out
why it was thought necessary.
Gideon
On 08/02/2010, at 2:41 PM, Jerry Krinock wrote:
>
> On 2010 Feb 07, at 15:42, Gideon King wrote:
>
>> So I think maybe there is a problem with me using my own custom managed
>>
On 2010 Feb 07, at 15:42, Gideon King wrote:
> So I think maybe there is a problem with me using my own custom managed
> object context in this way, and perhaps when it migrates the persistent
> store, maybe somewhere there it reverts to a standard managed object context
> or something.
>
> D
I'm having a problem that shows up when I do a Save As on my core data based
app. Saving my document is fine, so long as I save under the same name (either
with a new document or one I have loaded), but when I do a save as, I get the
following error:
malloc: *** error for object 0x114e74cb0: po
