Hi:
Sorry for the offtopic discussion but I think this still might be a good forum to ask this question.

I have a Demographics table in my DB which currently has a foreign key relationship with tables like Employee, Administrator etc.So the hibernate persistence class Employee 'contains' Demographics and there is EmployeeID field and a constraint in my Demographics table.

However, the requirements are likely to change and more Entities may contain Demographics in future but I dont want to keep adding columns to my Demographics table. I would still like Employee to contain Demographics in its object hierarchy, so the logical relationship is maintained in the object model.

Any advice on implementing this in DB would be great

Tia

splash

See the section of the reference docs on parent-child relationships and on inheritance. If you had a base class, say Person, for employee or administrator then you could use 2 of the 3 supported inheritance mapping strategies and not have to add new fk columns to the Demographics table.