As a new feature, it would be nice to have an optional attribute of the "inverse-foreignkey" element of a collection descriptor that maps it to a field of the class-descriptor it is contained in - instead of using the primary keys of the class descriptor.
Sometimes, the keys don't match up perfectly between tables... (this very well could be a normalization issue, but I have to work w/ it).
I have worked around it by using custom attributes.
So - it would be nice to see:


<inverse-foreignkey field-ref="collectionClassField" parent-field-ref="classDescriptorField"/>

So if the parent-field-ref attribute is present, OJB would use a different field as the key instead of the primary key...

What does everyone think?

--Bobby



Reply via email to