Thanks, Ben. I hear what you are saying about the draw tool, and,
yes, I have played with it extensively. In fact, I fancy myself an ER/
UML/Schema draw tool expert, and I'm afraid, the current Apple draw
tool is a nice start, but has a long ways to go before I would
consider using it on
You seem to have mistaken the modeler for a design tool. It's really
an implementation tool. There is nothing you can do with Core Data
that you can't do with the modeler. There is also nothing you can do
with the modeler that you can't do with Core Data (well, besides leave
attribute or
On Sep 17, 2009, at 09:21, Leon Starr wrote:
But if there is no @property/@dynamic for license in my Truck
subclass, (only in the Auto subclasss) I cannot access
thisTruck.license without getting a compiler error. Which makes
total sense to me since one NSManagedObject subclass (Truck) is
Not yet, anyway ;) But, yes, I agree with you. As it is, Core Data
is purely an implementation tool. And from what I can see so far, an
excellent one.
- Leon
On Sep 17, 2009, at 9:38 , Kyle Sluder wrote:
You seem to have mistaken the modeler for a design tool. It's really
an
NOW, I get it. Thanks! Problem solved.
(I knew you guys were seeing something I wasn't, so I'm glad I
persisted - no pun* intended).
- Leon
*okay, intended
On Sep 17, 2009, at 9:49 , Quincey Morris wrote:
On Sep 17, 2009, at 09:21, Leon Starr wrote:
But if there is no @property/@dynamic
On Sep 17, 2009, at 9:21 AM, Leon Starr wrote:
So, going back to my example, (and the part everyone disagrees
with!) I still don't get it. More importantly, my objc compiler
doesn't get it! In the model, Auto.license is properly inherited by
the Sedan and Truck subentities. No trouble
I've got a generalization in my core data model with entities named A,
B, C let's say where A is a super class with subentities B and C.
A is not abstract, so if I create an A NSManagedObject, I need to
create and relate a single B or C subclass object. How do I make this
happen? I can
On Wed, Sep 16, 2009 at 10:53 AM, Leon Starr leon_st...@modelint.com wrote:
A is not abstract, so if I create an A NSManagedObject, I need to create and
relate a single B or C subclass object. How do I make this happen? I can
create the entities, but HOW do I tell the model that object B is a
Hmm. Does that mean that I only need to create the subclass entity B
as shown?
// NSEntityDescription *aEntity = [[model entitiesByName]
objectForKey:@A];
NSEntityDescription *bEntity = [[model entitiesByName]
objectForKey:@B];
//A *newA = [[A alloc] initWithEntity:aEntity
On Sep 16, 2009, at 10:53, Leon Starr wrote:
I've got a generalization in my core data model with entities named
A, B, C let's say where A is a super class with subentities B and C.
A is not abstract, so if I create an A NSManagedObject, I need to
create and relate a single B or C subclass
?
- Leon
From: Quincey Morris quinceymor...@earthlink.net
Date: September 16, 2009 11:22:46 AM PDT
To: cocoa-dev cocoa-dev@lists.apple.com
Subject: Re: How to create subentity object inheriting from
superentity object in core data
On Sep 16, 2009, at 10:53, Leon Starr wrote:
I've got
On Sep 16, 2009, at 14:55, Leon Starr wrote:
Okay, guys, this helps a lot, still stuck, but getting closer! Now
I am getting an error with my revised code. We are talking about
two entities A and B where B where A is the parent of B.
A has the property name, and I would like to set that
Okay, my understanding, then, is that the inheritance is just in the
model - makes sense. If you subclass NSManagedObjects for the parent
and child entities, you need to explicitly declare and synthesize
(dynamically) all common properties you want to access at lower levels
of the
On Sep 16, 2009, at 18:38, Leon Starr wrote:
To get this to work, without KVC, I need to declare @property/
@dynamic for license in Auto, Sedan and Truck. (Can't just put it
in Auto and expect Sedan.license to work). No big deal unless I
have a bunch of common properties in the parent
I've got a generalization in my core data model with entities named A,
B, C let's say where A is a super class with subentities B and C.
A is not abstract, so if I create an A NSManagedObject, I need to
create and relate a single B or C subclass object. How do I make this
happen? I can create
Okay, my understanding, then, is that the inheritance is just in the
model - makes sense. If you subclass NSManagedObjects for the parent
and child entities, you need to explicitly declare and synthesize
(dynamically) all common properties you want to access at lower levels
of the hierarchy (at
16 matches
Mail list logo
