Hi,

We are using hibernate during the design of our project.

As the current database model stands, it appears that if natural keys are used as primary keys it would make querying easier.In addition we plan to denormalise some data as we wish to avoid complex joins and reduce time execution of the query.

The problem is we need to make a decision on usage of composite keys in a table, as due to the use of natural keys , most tables will need to have a composite key.

We need to know in hibernate what are the pros and mostly cons of using composite keys.

There are 2 approaches in our mind.

1. Use the hibernate composite keys as recommended, ie.

<composite-key>
<key-many-to-one id=address class=address lazy=true>
<composite-key>

Here we wish to avoid a join on address table.how do we achieve this, as we understand lazy will not query address table howver if we call getkey it will then load the address table along with other keys which form part of the composite key.
We want to avoid this, can we avoid it, as we always need to call getkey

2. Use hibernate composite keys in a workaround manner.

In order to ensure that hibernate does not fire a join, define composite keys as
<composite-key>
<key-many-to-one id=address column=address>
<composite-key>

i.e use as a regular key without mapping to parent table to avoid the join.

Could you please tell me the best approach from design point of view and problems with hibernate composite keys.

THIS IS URGENT , PLEASE HELP

You could just map the composite key without it pointing to the parent.

i.e.

in a very sql-maps kinda way. eliminating the benefits of hibernate.

but if you ever wish to traverse the relationship in an object oriented manner, or ever want hibernate to run this join, you won't be able to