> Can't you have the primary key of C also be the foreign key > to B? This way you only have 1 key column. Just a thought...
original we wanted it exactly like that, but then we cant use extents and the "Mapping Classes on Multiple Joined Tables" strategy. >From the OJB advanced technique docs: "Be aware that this sample does not declare org.apache.ojb.broker.B to be an extent of org.apache.ojb.broker.A. Using extents here will lead to problems (instatiating the wrong class) because the primary key is not unique within the hiearchy defined in the repository." greetings Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
