Hi everybody,
I'm using Hibernate 3.3.2 with Oracle 10g.
I have a table A without primary key defined (don't tell me why, legacy system...).
A has 14 fields, so hb2ddl tool created two Classes: A and AId, where the latter is the set of all the table's fields. Among these fields, only 3 have the not null constraint.
The problem is: whenever I query the table, Hibernate finds the correct number of tuples, but if one ore more fields of a tuple were null, the entity is not instantiated and the criteria.list() return List has a null entry.

Does anybody can tell me why?

Here is an example taken from the logs (TRACE level). If CAPTION is not null I have


If CAPTION is null


So at the first NULL met, the tuples seems to be abandoned

The table data type are all numbers or char or varchar, so the JPA entities have nothing in particular.
Any help would be really appreciated!
Thanks,
Ariminum

I think it should not be possible to have nullable fields in an composite primary key. SQL Server complains to me every time I try to create a table like that.

How would you identify two tuples that have the same values and both have null in the nullable column? If that exists the column is not useful as a primary key => use only the not-null columns as primary key...

Hi kossmo,
thanks for your reply.
I totally agree with you: from a relational point of view, this is completely wrong, but I cannot change the db schema (old vb6 applications using it...)
What I was asking myself is if I forgot something, because Hibernate does not give any error or warning, so I was worried about it.
Now I solved specifying in the reveng.xml a <primary-key> based on two non nullable fields.
Paolo