一个Person可以参加多个Event,一个Event有多个Person参加。
映射文件如下:
< hibernate-mapping package ="events" >
< class name ="Person" table ="person" >
< id name ="id" column ="person_id" >
< generator class ="native" />
</ id >
< property name ="age" length ="0" />
< property name ="firstname" />
< property name ="lastname" />
< set name ="events" table ="person_event" >
< key column ="person_id" />
< many-to-many column ="event_id" class ="events.Event" />
</ set >
</ class >
</ hibernate-mapping >
< hibernate-mapping >
< class name ="events.Event" table ="events" >
< id name ="id" column ="event_id" >
< generator class ="native" />
</ id >
< property name ="date" column ="events_date" type ="timestamp" />
< property name ="title" column ="events_title" />
< set name ="participants" table ="person_event" inverse ="true" >
< key column ="event_id" />
< many-to-many column ="person_id" class ="events.Person" />
</ set >
</ class >
</ hibernate-mapping >
inverse=true的含义: 由双向关联另一方维护该关联,己方不维护该关联(只能进行查询操作)。在上述代码中,由Person方维护该<many-to-many>关系,示例代码如下(以向Person参与的Event中加入新的Event为例):
session.beginTransaction();
Person p = (Person) session.load(Person. class , personId);
Event e = (Event) session.load(Event. class , eventId);
p.getEvents().add(e);//执行该代码时,hibernate会向中间表 person_event中插入person_id和event_id记录,如果换成e.getParticipants().add(p)的话,该代码将不会被执行,即hibernate不会向表person_event中插入记录。
session.getTransaction().commit();
建议大家好好去看一下这个链接,讲的很详细,虽然是E文,可并不难懂。
http://www.hibernate.org/155.html
这篇文章里没有提到delete的情况,我就one-to-many来做个简单说明:
- Parent parent = (Parent) session.load(Parent.class, pid);
- session.delete(parent);
1. 爸爸那边设置了cascade=all和inverse=true
a. delete from children
b. delete from parent
2. 爸爸那边设置了cascade=all,没有设inverse=true
a. update children set parent_id=null where parent_id=?
b. delete from children
c. delete from parent
因为此时inverse=false,所以爸爸要负责维护relationship,所以它要去把children中的连接信息都清空。但是,如果children的parent_id的constraint设置的是not-null的话,那么很不幸,hibernate执行到2.a就会throw exception了。
如果你要问,这个inverse=true到底是在源代码中的哪儿判断的呀?请看代码:
- ......
- SessionImpl.flush();
- SessionImpl.execute();
- SessionImpl.executeAll(collectionRemovals);
- executable.execute();
- ScheduledCollectionRemove.execute();
- getPersister().remove( getId(), getSession() );
- OneToManyPersister(即AbstractCollectionPersister).remove();
- if ( !isInverse ) {
- PreparedStatement st = session.getBatcher().prepareBatchStatement( getSQLDeleteString() );
- }
- OneToManyPersister.getSQLDeleteString();
- return "update children set parent_id=null where parent_id=?";
- ......