Is it bug or feature?

ko5tik · **Posted:** Fri Mar 19, 2004 11:39 am

I'm using hibernate 2.1.2 , and discovered that this mapping causes
problem while flushing.

Course.hbm.xml:

Code:

   <bag name="groups" lazy="true" cascade="delete">
      <key/>
      <one-to-many class="com.infodesire.educator.data.Group"/>
    </bag>

Group.hbm.xml:

Code:

<many-to-one name="course" not-null="true" cascade="none"/>

I create group following way:

Code:

          Group group = new Group();
            course.getGroups().add(group);
            group.setCourse(course);

            Session session = obtainSession();
            session.save(group);
            returnSession(session);

Then while flushing session, it tries to update collection
and botches primary key instead updating foreign key:

Code:

[main] DEBUG net.sf.hibernate.SQL  - update course_group set id=? where id=?
Hibernate: update course_group set id=? where id=?
[main] DEBUG net.sf.hibernate.impl.BatcherImpl  - preparing statement
[main] DEBUG net.sf.hibernate.type.IntegerType  - binding '1' to parameter: 1
[main] DEBUG net.sf.hibernate.type.IntegerType  - binding '1' to parameter: 2
[main] DEBUG net.sf.hibernate.impl.BatcherImpl  - Adding to batch
[main] DEBUG net.sf.hibernate.type.IntegerType  - binding '1' to parameter: 1
[main] DEBUG net.sf.hibernate.type.IntegerType  - binding '2' to parameter: 2
[main] DEBUG net.sf.hibernate.impl.BatcherImpl  - Adding to batch

When I specify column names explicitely on both sides, everything is fine.

And dtd says that column names for foreighn key are implied...
Is it minee fault or yours?

emmanuel · **Posted:** Wed Mar 24, 2004 6:10 pm

<key> column is not optional