hql size seems not to be consistent with size() method

alcarraz · **Joined:** Mon Apr 05, 2004 3:06 pm **Posts:** 2

First of all thanks for your work, it has been really useful for me.
Making tests i've noticed an inconsistentcy between size keyword of hql and size method of hibernate lists.

Let me introduce the case, making test i accidentally added rows to a collection without respecting the correlative index field.

When executing the test i've noticed that the List.size() method was returning one unit more than the size in hql, i didn't understand at the begining but few minutes later i saw that what was happening is that the hibernate list was considering as null the missing indexes, this seems to be ok but if this is the case shoudn't the size keyword consider this elements too?

I think size of HQL should return max() of the index field of the collection plus one instead the count of the rows.

do you agree?
should i add a new issue in jira?

On the other hand I voted for a related issue really important to me, which is the posibility of filter collections of composites.

thank you very much in advance

Andr

emmanuel · **Posted:** Wed Apr 07, 2004 6:03 am

Unfortunatly HQL size() refer to the SQL semantic and thus may be inconsistant with list semantic.
Add it to JIRA but I'm not sure it will be accepted.

alcarraz · **Joined:** Mon Apr 05, 2004 3:06 pm **Posts:** 2

Thanks for the response but i've got another question:

but what would be the form of getting the size without initializing the list otherwise?
is there someone planning to work with issue HB-467? to filter on collection of composites?

Thank you very much

Andr

emmanuel · **Posted:** Thu Apr 08, 2004 8:35 am

I don't think

Code:

select maxindex(order.items) from Order order

works.
But you can do a pure SQL query using session.connection()