If you have an ordered list (a <list> with a hibernate generated <index> column) is it necessary to get automatic ordering to work to add the object to that list explicitly?

Why I ask is that Parent/Children type of relationship where it is easier for me just to set the parent rather than add to the children, but in that case the ordering doesn't seem to function properly.

Is this expected behaviour or am I doing something wrong?

Thanks alot.

Matt

Please be a bit more explicit about what you are doing and what your mapping looks like.

Sure Gavin. In this case the parent/child is a self join that looks like this:

<property name="order" column="CNT_CHILD_ORDER" type="int"/>

<many-to-one name="parent" column="CNT_PARENT_CONTENT_ID" class="blah.blah.Content"/>

<list name="children" lazy="true">
<key column="CNT_PARENT_CONTENT_ID"/>
<index column="CNT_CHILD_ORDER"/>
<one-to-many class="blah.blah.Content"/>
</list>

I originally had the list set as inverse and was just setting the parent, but this resulted in incorrect ordering (or no ordering at all). So my question is, for the ordering index column to be set properly by hibernate do I need to explicitly add the Content object to the list of children, or is simply setting the parent enough and hibernate will figure it out?

I appreciate the help.

Matt

Hibernate (and jdo, etc) don't implement "managed relationships" so yes, you need to adjust both ends.

Ok, thanks for clearing that up.