Hibernate version: 3.2.1 GA

It seems that Hibernate is incorrectly computing the size of an association in a particular case. I have an entity "List" that has a set of "Users" (subscribers). Users have an "information" field that is NULLABLE.

When I do myList.getSubscribers().size() it generates a correct query but counts the non NULL lines and returns an incorrect count.

Adding "nullable = true" to the @Column annotation did not help.

Does someone encountered the same problem before?

Are you saying that users with information = null are not subscribers and should not be in the list? You can add a where="information is not null" in your mapping to do that.

If the problem is that you want the collection to contain all associated users, but you want to count only the ones where information = null, then you'll have to do that manually. Loop through the collection and count the relevant ones yourself.

All the users that join should be in the 'subscribers' collection, regardless of the information field being null or not.

The mapping look like



but when Hibernates queries the database and counts the number of rows, it select the last column and counts the non NULL entries. The last column happens to be a nullable one, thus yielding an incorrect count.

Thanks for your help! PL

Just checked the code, and hibernate doesn't check that the column it uses for the getSize() query is not null. IMO that's a bug.

Your options are either to load the collection before calling size() (because the actual collection size is used then), or change the order that fields are mapped in. I haven't followed the hibernate code all the way, but it just selects column 0 from the mapping to use in the count clause: if you change what that column is, it should work. The only reason it wouldn't work is that hibernate sorts the columns when creating the mapping.

Thanks! That's what I thought, but happy to see that a pro can verify.

PL