On the logical level it does not matter if a foreign key to C "comes from" A or B.
But in this case, I need a foreign key inside table C to table A or B, because classes A and B have a collection of C.
It is like a 1-n relation from (A union B) to C.
I think the most clean solution would be to have one FK pointing to A, and one FK pointing to B.
Can I have declare a reference in OJB in case A and B have no common super class?
from the 1 side (i.e. collection-descriptors A and B) it is no problem at all.
The only problem could be with the n side (reference-descriptor in C).
If you are using two FKs (one to A and one to B) there won't be any problems with the reference-descriptor as well.
-Thomas
Olli
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
