Hibernate version:3

Mapping documents:

<hibernate-mapping package="pack">
<class name="A" table="A">
<composite-id name="Apk" class="A_Pk">
<key-property name="grId" column="GRID"/>
<key-property name="vid" column="VID"/>
<key-property name="note" column="NOTE"/>
</composite-id>

</class>
</hibernate-mapping>

I also have a primary key class named A-Pk which implements serializble and also has all the primary key properties of A.

Code between sessionFactory.openSession() and session.close():

Query query =sess.createQuery("Select A from A a where a.apk.vid = "2+ "and a.apk.grId = 5");
Full stack trace of any exception that occurs:
Now If there is not null value of each of the columns in the A table I get desirable results . but the place where I have NOTE as null . I get null object back. I get the right number of objects but all those objects are null.
Where as what I want is that it should return the right number of objects with right property values. If one of the column has null value, it should return null value for that column but not for the whole object.
As I read in the docs , they say all the properties in the composite key should be not-null incase you are using "Set" but otherwise its fine.
Now Im using a list and it should be fine with that.
Can anybody help?
Any possible way out?

I know there were some issues on composite ID which claimed to be fixed in v. 3.1.3

I had exactly the same issue where I put a column in the composite id that could be null. I moved it outside the composite-id and just made it a normal property and that fixed the issue. The database generally doesn't allow a null in a primary key column anyway so it makes sense that if a column can be null then it shouldn't be in the composite-key. I guess there's always a use case for having a null in the composite-id but maybe you can live with moving it outside the composite-id?

Thanks guys it helped. I realised that we cant have nullable column in composite key.
Anyways I had to apply the logic programmatically.
Thanks for help
Cheers!!

So ... what does one do if one needs to return a list of unordered/maybe duplicated records from database?

Given Hibernate:
1: Always need a ID for class mapping
2. Cannot have null in composite-id

I'd be surprised if this will seem an impossible task for Hibernate !?

regards

How can i take a property out of <composite-id> ?