Hello. I use Hibernate 3.2.1ga and found a problem while mapping entity for legacy database. Entity has a composite primary key with 6 columns:
- project name
- project version
- activity name
-resource name
which are not-null and
- start date
- finish date
any of which/or both are nullable.

When Hibernate fetches from database entities which have one-to-many relation to this one, the target collection is empty but as I can see SQL performed by Hibernate gives me in sqlplus 1 record whith "start date" (for example) = null. If I change both columns values in database to be not null, Hibernate gives me a collection of 1 element. It seems that Hibernate does not create a Java object and event its Id object if any of primary key columns is null.

Does Hibernate provide an ability to work with tables which have composite IDs with nullable column? How to resolve the problem?
Thanks in advance

Hi,

I'm having the same problem. All records are fetched from the database, but only those with all PK columns not null are loaded into the OneToMany list.
EntityManager.find() with some PK columns being null works fine.

Same here too... but in my situation, that nullable column of my composite key is there to make the entire row unique, so the option of excluding it is not really feasible.. someone, anyone help us..

I don't think Hibernate will work with PK or in your case Composite keys having null value. I had this issue before and I was wondering why I was not getting result on some of the rows. Then I was told that it was because I had null values in the PK.

So.. any proposed solutions? (no no no... not pure jdbc...)