Hi Bruce,
Thanks for all of your hard work on this project
and for answering so many emails. It is really
much appreciated.
My new question is what is the status
of "Foreign key as part of primary key" bug 925.
Please tell me if I have summarized the bug
correctly as follows:
I have a table Master with MasterId primary key.
I have a dependent table Detail with a primary
key of MasterId.
Detail.MasterId is a foreign key to Master.MasterId.
Assuming I have diagnosed the bug correctly, I assume
that the solution is to create a surogate primary
key on Detail (called DetailId for instance) and then
Detail.MasterId will no longer be part of the primary
key.
Assuming that the above surogate key work arround is
valid, my problem is that I am implementing an application
against an existing schema that another app is
already using. I therefore can not change the schema.
I have an additional problem that I wonder if it is also
a bug. I have a compound primary key in the Detail table.
Detail.MasterId and Detail.Attribute.
I have declared an array of Detail objects in the Master
table.
I am getting the following error:
org.exolab.castor.mapping.MappingException: The number
of column of foreign keys doesn't not match with what
specified in manyKey.
Is this the same bug as 925 or is there another bug
related to compound primary keys.
Thanks,
Ron
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
