This is beyond doubt. I read somewhere once that there's a fluky
thing wherein the order of the entities alphabetically within the
model matters. Hence my parent entity begins with "A" and is the
very first entity in my model. Doesn't help.
I don't recall that.
I can confirm this is not the case, actually. I have at least one
model I know of where this isn't true.
I have had it working for weeks by making AbstractResource non-
abstract and that gets me past the throw but it causes me problems
in other areas (i.e. a fetchRequiredXXX against Resource returns
two copies.) I'm coming back now to do this "the right way" and
make single-table inheritance with an abstract parent work as I
imagine it should.
Adding a unique restricting qualifier to the abstract entity should
avoid the duplicates. I don't recall running into this.
Yeah, I've never seen this either. +1 for "goofy model"
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
