On 05/11/2008, at 6:25 AM, Lachlan Deck wrote:
On 04/11/2008, at 8:50 PM, Paul Hoadley wrote:
I have another clue. Thanks for bearing with me.
On 04/11/2008, at 6:27 PM, Paul Hoadley wrote:
Maybe I need to start again from scratch.
Just to recap:
1. I have a framework that contains a model Auth that contains an
entity Person. It also contains the UserPreference entity that has
a to-one relationship to Person. Person is abstract.
2. I have an app that contains a model AMAuth that contains an
entity AMPerson. I created AMPerson by subclassing Person in the
Auth model (nominating HI), and then cut + pasting over the entries
for AMPerson in index.eomodeld, and AMPerson.plist to the AMAuth
model. I changed the package on the class appropriately. (Is
there an easier way to generate a cross-model sub-entity?)
3. I have set up the tables using the SQL generated by Entity
Modeler. This creates both 'person' and 'amperson',
That is not horizontal inheritance to my understanding. You have
Vertical inheritance and so you've not modelled it correctly. Person
should not have a table for Horizontal.
So Chuck says for Frontbase "It does for FrontBase as the PK
generation sequences as associated with a physical table in FrontBase.
". That's puzzling to me. i.e., AMPerson is a physical table. Why does
the parent need to map to a physical table at all for HI?
Or are you saying for HI that the pks are sequential across sub-
entities for frontbase?
He's using postgres however...
with regards,
--
Lachlan Deck
_______________________________________________
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]
