[b]Hibernate version:[/b]
2.1
[b]Mapping documents:[/b]
<class name="Association" table="ASSOCIATION">
<id name="id" column="ASSOCIATION" type="integer">
<generator class="native"/>
</id>
<property name="parentProfileId" column="PARENT_PROFILE_ID" type="integer" not-null="true" />
<property name="childProfileId" column="CHILD_PROFILE_ID" type="integer" not-null="true" />
<many-to-one name="parentProfile"
class="Profile"
column="parent_profile_id"/>
</class>

This code :
assoc.setParentProfileId(parentId);
session.update(assoc);
Doesn't do anything.
Before I've added the many-to-one relation it worked ok.
Why is that?

Thanks a lot

[b]Debug level Hibernate log excerpt:[/b]
[DEBUG] (SessionImpl.java:1340) object already associated with session

<generator class="native"/> and assoc.setParentProfileId(parentId);
is strange... never forget tha tyou're working with objects not datas


is assoc detached?

[quote="anthony"]<generator class="native"/> and assoc.setParentProfileId(parentId);
is strange... never forget tha tyou're working with objects not datas

[quote]session.update(assoc); [/quote]
is assoc detached?[/quote]

I don't understand what is the problem...
parentProfileId is not the primary key for Association.
Before I introduced the many-to-one relation everything worked ok.

I use Spring and that was happening in a:

TransactionTemplate transactionTemplate = new TransactionTemplate(this.transactionManager);
transactionTemplate.setPropagationBehavior(TransactionDefinition.PROPAGATION_REQUIRED);
transactionTemplate.execute(new TransactionCallbackWithoutResult() {
public void doInTransactionWithoutResult(TransactionStatus status) {
...
}
}

should be



parent should be transparent as managed by the many to one association

[quote="anthony"][code]<class name="Association" table="ASSOCIATION">
<id name="id" column="ASSOCIATION" type="integer">
<generator class="native"/>
</id>
<property name="parentProfileId" column="PARENT_PROFILE_ID" type="integer" not-null="true" />
<property name="childProfileId" column="CHILD_PROFILE_ID" type="integer" not-null="true" />
<many-to-one name="parentProfile"
class="Profile"
column="parent_profile_id"/>
</class> [/code]

should be

[code]<class name="Association" table="ASSOCIATION">
<id name="id" column="ASSOCIATION" type="integer">
<generator class="native"/>
</id>
<property name="childProfileId" column="CHILD_PROFILE_ID" type="integer" not-null="true" />
<many-to-one name="parentProfile"
class="Profile"
column="parent_profile_id"/>
</class> [/code]

parent should be transparent as managed by the many to one association[/quote]

That was a great suggestion, but didn't solve my problem :(
I've changed tha mapping and the coresponding bean and now I set parentProfile with a reference to the new desired profile not only it's id, but I get the same debug message:
[i]object already associated with session[/i]

again; is your instance detached? or is it already in the session?

if your object is already in the session, no need to call update... be sure to understand all this update != SQL UPDATE

How do I check if it's detached or not?

you should read Hibernate in Action, this is a friendly advice.

good advice :)
I have the book in front of me and now I understand what a detached instance means.
I'll came back if I have more questions related to this particular problem of mine.

no problem ;)