Good afternoon.
As the project I'm working on has grown, one of the domain objects is growning a bit large for some folks taste (70 fields). This of course translates to 70 columns in the DB.
We're having a debate over how to manage this... The attributes all clearly belong to the entity in question, so I content they all belong in one table, and we should use components to compose the entity, making it more manageable while not disrupting the db structure.
Others contend that we ought to break the table into multiple smaller tables and join them with 1-1 relationships.
I see the second strategy as causing issues with uneeded joins, issues when constructing queries, etc.
I'm looking for opinions from the community to help settle this debate. Any input is greatly appreciated.
Thanks
Hibernate version: 3
Name and version of the database you are using:MySQL 4
|