We are designing a database with this new-fangled Hibernate tool in mind.
The database has a ClientHeader object/table with fields like firstName, lastName, ssn, etc.
We also have a ClientDetails object with info like dob, weight, hairColor, etc.
Simple so far:
The ClientDetails object started off with a few object members (sets) like Adress, Contact Info (to hold multiple addresses, phone numbers etc). HOWEVER
Now we have about 35 object members for ClientDetails ( like MilitaryHistory, Aliases, Children, blah, blah, blah.) The ClientDetails object is now HUGE!
I think we get an A+ for our object oriented thinking, but I think we've created a monster as far as Hibernate goes.
The question: If we define the relationships (as described above) is Hibernate going to look in all 35 (or 36 with parent) tables everytime we want to look at something in the ClientDetail table?
If we just want a zip code from ClientDetail.Address, do Hibernate have to look up every other table (MilitaryHistory, Children, Alias, and the other 30-some-odd) ?
Thanks
[ October 18, 2004: Message edited by: chris gar ]