I have a problem where a child collection is being populated with 166 null objects when the database only has one.

I have one parent record with one child. When the parent is loaded it load 166 child records and the last one is populate.

I can figure out why there are so many children. The sql statments are returning the correct record but it seems that the child query is being executed multiple times.

Any suggestions would be greatly appreciated. Here is my mapping of the child collection.

<list name="CurrentDosageDetails" inverse="true" lazy="false">
<key column="MedDosHdrId" />
<index column="MedDosDtlId" type="Int32" />
<one-to-many class="MedicationDosageDetail, Entities" />
</list>

What does the index column contain ? 166 ? Then the object is inserted at index 166 in the list and the items from 0 to 165 are filled with null.

Is there a way to turn that off or must I use a SET to get just the records I have in my database?

Also is there an example of where you want a collection populated with nulls when no objects exist?

Thanks for the reply.

No switch. You can use a bag or set. The main question is, what your "index" is for. If it's not really necessary for positioning/ordering the elements, the you can safely switch to a bag or set.



I admit it looks a bit strange on the first view. But when you think a bit about it, it's the only logical way. Either that column is an index for your collection than hibernate has to put the element at this position or it's not an index and then your "list" isn't really a list (from a semantical point of view).

Thanks. That was exactly what I needed.