Thanks for the test project. However, reviewing and fixing all
compiler warnings is likely to make development a significantly less
frustrating experience. We've taken to fixing (nearly) all compiler
warnings, even ones we know are harmless, so we can easily find the
new ones that likely
Adding an inverse does solve the problem (maybe I missed mentioning
it). The reasons why I thought it was a CD bug are the following:
- I don't think it's obvious from the docs that the SQLite store can't
cope with relationships that have no inverses (I was told by Danny
Greg that having an
Hi all,
Coming back to my original question (http://www.cocoabuilder.com/archive/message/cocoa/2009/9/13/244940
), I isolated a reproducible case whereby CoreData loses a
relationship on save (only when using SQLite). Link to the sample
project is included below (check out the README for an
On Sep 13, 2009, at 9:14 AM, Milen Dzhumerov wrote:
-(void)awakeFromFetch
{
for(id base in [self relationship])
Log(@%@, base);
...
}
awakeFromFetch
[...]
Important: Subclasses must invoke super’s implementation before
performing their own initialization.
On 13 Sep 2009, at 17:45, mmalc Crawford wrote:
On Sep 13, 2009, at 9:14 AM, Milen Dzhumerov wrote:
-(void)awakeFromFetch
{
for(id base in [self relationship])
Log(@%@, base);
...
}
awakeFromFetch
[...]
Important: Subclasses must invoke super’s
I've been trying to track down a bug and it *seems* that it might be
CoreData's fault (I highly doubt it but there's a small chance). I
have the following configuration:
- A base class, let's call it Base
- A subclass of Base, let's call it Subclass
Subclass has a to-many relationship to Base.
