Greetings,
First of thanks to the OJB developers for all the hard work. I am really
enjoying working with OJB and think it is a great product.
Next, I just wanted to report what I think may be a defect with
field-id-ref.
The documentation defines field-id-ref as:
"The field-id-ref contains the id attribute of the field-descriptor used
as a foreign key."
But in working with it, it seems that it might instead be the nth item after
the id attributes are sorted.
For example, if I am have attributes defined as follows:
<field-descriptor id="1" name="reportDataId" column="REPORT_DATA_ID"
jdbc-type="INTEGER" primarykey="true" autoincrement="true"/>
<field-descriptor id="2" name="deviceId" column="DEVICE_ID"
jdbc-type="INTEGER"/>
<field-descriptor id="3" name="formId" column="FORM_ID"
jdbc-type="INTEGER"/>
<field-descriptor id="4" name="antotherId" column="XXX_ID"
jdbc-type="INTEGER"/>
and a reference-descriptor:
<reference-descriptor name="form"
class-ref="com.cogent.bo.fieldpro.FormImpl" table="mdp.FORM" >
<foreignkey field-id-ref="3"/>
everything works fine.
If I then go back and comment or remove the second field-descriptor, it
seems that OJB is now attempting to use field-descriptor with the id of 4
(which is the the third in id sorted sequence) to resolve the join.
Is there anyway to verify this with the unit tests ?
Gary
--
To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
