Hi I have a problem with nulls appearing a the begining of my list of SelectedFees when they are retrieved from the database.

There are no extra rows in the database. The only thing i can think of is null objects are being cached somewhere an not being removed??

Any help would be much appreciated.

cheers



The mapping for this list is below.

Hibernate version: 3.1

Mapping documents:

<list name="fees" lazy="false" cascade="all-delete-orphan" optimistic-lock="false">
<key>
<column name="ENQAPPID" />
</key>
<list-index column="IDENTIFIER" base="1" />
<one-to-many
class="fee.SelectedFee"/>
</list>

Hi

what cacheing you are using. and send mapping file and code


Amila

Hi amila733

Thank for you response. I think I have found the problem. It seems that if I have one row with id 7 in my database table then 6 nulls are added before the actual selected object in the list.

No idea why this is happening. Very strange if you ask me.

I've had this problem before. it's happening because you're using a list collection type. A list is an ordered collection that defines it's ordering based on the list-index-column you provide. If you have one row with an index of 7, hibernate will say 'OK, this is an ordered list, and this element is in position 7'. Therefore it will create a list object with a length of 7 were the first 6 entries are null (as there is not data for those indicies). This is all so that the semantics of the 'list' type are preserved.

If the ordering is significant within your application, then you need to make sure that you are maintaining the index column correctly. If is not, then you can avoid this problem by using one of the unordered collection types, such as a set.

Jason.