Hi everyone,

i'm trying to order elements of a one-to-many relation

say
<class name="DossierFormation" table="DOSSIER_FORMATION">

<set name="engagements" inverse="true" lazy="true" sort="EngagementComparator" cascade="all-delete-orphan">
<key column="ENGAGEMENT_DOSSIER_FORMATION_ID_FK"/>
<one-to-many class="org.xx.engagementremboursement.model.Engagement"/>
</set>
<class>

So I currently have a sorted set.
the problem is that I create to many engagement at once and they all have the same date. So many are not included in the TreeSet().
Moreover I have to implement a compareTo() method in the automatically generated Engagement class, due to the TreeSet (only implementation of sorted set). So it breaks the automatic process.

I've got no field that can be use as index, except the id, but it doesn't exist when the object is transcient.

I was thinking of using a list mapping and thus creating a dedicated index column but I can't find in the doc whether I'll have to fill this attribute or if it will automatically inserted and incrmented by hibernate at creation time?

any input on this??

thanks,
nodje

The index column will of course be automatically managed by Hibernate. Note however that Lists are really not good and not officially supported for parent-child relationships, should this be one.

what do you mean by "not officially supported", it's in the documentation right?

Why is it so bad?

It is also in the documentation that it is not supported, right at: http://www.hibernate.org/hib_docs/reference/en/html/collections.html#collections-bidirectional - No problem for unidirectional associations though