From an OJB point of view you can well keep both classes in one table. There is a sample on how to use a RowReader for this in tutorial 3.
We are currently working on a Solution for nested Attributes that will make such things even more easy.
But from entity relationship modelling point of view it is much cleaner to keep both classes in separate tables.
It will avoid data redundancy.
cheers,
Thomas
Rex Madden wrote:
I have a table called CUSTOMER which I would like to have broken down
into two classes: 1 called Customer and 1 called Address. The Customer
class would obviously hold the basic customer info, and then the Address
class would hold info for the user's billing address and the user's
shipping address. But all of this would be on 1 table. Is there any
way to map this? Or am I better off having an address table?
Thanks,
Rex
-- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
