Hibernate version: 3.2.2

Name and version of the database you are using: Oracle 10g

I've an Oracle view with 6 columns: name, id, company, department, reference, creationdate. I used all the columns (some columns are nullable) as the composite-id.

Is it ok to have nullable fields in composite-id or all fields in composite-id must be not-null?

In the view, there's a row with name & id, and when I try to query by criteria using these 2 fields, a list of 1 null object was returned. My mapping is as below:



It is right that 1 object should be found, but it was null, does it means that Hibernate is unable to instantiate the object? I've the default constructor, a private attribute for the composite-id object (with getters/setters) and getters/setters and private attributes for all fields in the class as well.

Or this there a better way to do this in Hibernate?

Answering my own question.

What we did was to create a view on this view, and use the Oracle ROWNUM column as the primary key and it works!

If you use this mapping document for onlt reading purpose then its fine. Becuase if we use rownum as id in hibernate mapping then we can't insert or update a unique record.

In select also you can't load the entity based on your id that is rownum. Hope you dont required this type reuiremnt.

Its not good design to create a table withouy keys..

As I said, this is a view, so its read only, hence no issue with using the ROWNUM. For legacy systems, it is sometimes unavoidable to have such cases (designs).