Hi,

I have class Document which has many-to-many back to Document. But this association table has extra column.

The main class looks like:

public class Document
{
private Long id;
private String name;
private Set parent = new HashSet();
private Set child = new HashSet();

... setters/getters
}


The association class is:
public class DocumentRel
{
private Document parent;
private Document child;
private String color;

... setters/getters
}

mapping is:

<class name="Document" table="doctest">

<id name="id" type="long" unsaved-value="null" >
<generator class="sequence">
<param name="sequence">doc_sequence</param>
</generator>
</id>

<property name="name"/>

<set name="parent" inverse="false" lazy="false" table="doctest_rel">
<key column="child_id"/>
<composite-element class="DocumentRel">
<property name="color"/>
<many-to-one name="parent" column="parent_id" class="Document" />
</composite-element>
</set>

</class>


The code is:


DocumentRel rel = new DocumentRel();
rel.setColor( "a" );
rel.setParent( doc2 );
doc1.getParent().add( rel );

session.save( doc2 );
session.save( doc1 );

The result is:

insert into doctest (name, id) values (?, ?)
insert into doctest_rel (child_id, color, parent) values (?, ?, ?)
delete from doctest_rel where child_id=? and color=? and parent=?
insert into doctest_rel (child_id, color, parent) values (?, ?, ?)

why is there inser, delete and again insert into relation table ? Why its not there only one insert ?

any help would be appreciated

This cannot be all the code. How do you get the references to doc1 and doc2? For you benefit (as well as ours in trying to help you) I suggest you come up with a simple main() that tries the use case where you are seeing this issue.