So long as partyperson doesn't need to be read to figure out its primary key, it should be fine. So if partypersonid is an identity, or has a default value like newId(), then you'll be fine. You can add a little hibernate-checked safety net by making all attributes in your partyperson table update="false", seeing as you're only ever going to insert into the table.
You may find that you don't need to map partyperson at all. Database triggers that create a partyperson row whenever a currentpartyperson row is inserted or updated will probably work, they'll be faster than hibernate, and they'll reduce the amount of java code you have to maintain.
|