Consider a dependent class DCurrencyValue with a reference to a Currency and a float 
value. If this class is an attribute of a persistent class, the only way to map such a 
dependent class is to write a specific FieldConversion for it, where the whole 
contents of the dependent class is converted to one field in the peristent class 
table. With this conversion the ability to check the referential integrity of the 
underlying database is lost. And if you want to select/ filter on the Currency of the 
DCurrencyValue, all the DCurrencyValue fields in the table have to be fluffed up.

It would be nice if it the current mapping could be extended so that the individual 
attributes of a dependent class are mapped to fields instead of just one field for the 
whole dependent class.

Best regards,

Pieter Gordijn.

Reply via email to