【SSH进阶之路】【十一】hibernate5 注解映射【3】一对多多对一双向关联

在上两篇文章里，我们详细地分别讲解了一对多和多对一的单向关联配置的具体属性含义，在这一篇文章里，我们完成两者的的整合建立双向关联。

在实际的博客网站中，我们可能需要根据文章读取作者（用户）信息，但肯定也要让用户能获取自己的文章信息，针对这种需求，我们可以建立文章（多）对用户（一）的双向关联映射。

下面先看实例映射配置文件：

//一方配置

package com.chenhao.hibernate.model;

import java.util.Set;

import javax.persistence.CascadeType;
import javax.persistence.Entity;
import javax.persistence.FetchType;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.JoinColumn;
import javax.persistence.OneToMany;
import javax.persistence.Table;


/**
 * 
 * @author chen_hao
 *
 */

@Entity//声明当前类为hibernate映射到数据库中的实体类
@Table(name = "t_user1")//声明在数据库中自动生成的表名为t_user
public class User {


    @Id//声明此列为主键,作为映射对象的标识符
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Integer id;
    private String name;


    @OneToMany(cascade = CascadeType.ALL,fetch = FetchType.LAZY,targetEntity = Article.class,orphanRemoval = true)//用户作为一方使用OneToMany注解
    @JoinColumn(name = "user_id")
    private Set<Article> articles;//文章作为多方，我们使用Set集合来存储，同时还能防止存放相同的文章



    public String getName() {
        return name;
    }
    public void setName(String name) {
        this.name = name;
    }
    public Integer getId() {
        return id;
    }
    public void setId(Integer id) {
        this.id = id;
    }
    public Set<Article> getArticles() {
        return articles;
    }
    public void setArticles(Set<Article> articles) {
        this.articles = articles;
    }
    //重写hashcode方法提高比较效率
    @Override
    public int hashCode() {
        final int prime = 31;
        int result = 1;
        result = prime * result + ((id == null) ? 0 : id.hashCode());
        result = prime * result + ((name == null) ? 0 : name.hashCode());
        return result;
    }
    //重写equals比较对象相等
    @Override
    public boolean equals(Object obj) {
        if (this == obj)
            return true;
        if (obj == null)
            return false;
        if (getClass() != obj.getClass())
            return false;
        User other = (User) obj;
        if (id == null) {
            if (other.id != null)
                return false;
        } else if (!id.equals(other.id))
            return false;
        if (name == null) {
            if (other.name != null)
                return false;
        } else if (!name.equals(other.name))
            return false;
        return true;
    }
}

//多方配置

package com.chenhao.hibernate.model;

import javax.persistence.CascadeType;
import javax.persistence.Entity;
import javax.persistence.FetchType;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.JoinColumn;
import javax.persistence.ManyToOne;
import javax.persistence.Table;


@Table(name = "t_article1")
@Entity
public class Article {


    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Integer id;
    private String content;

    /**
     * @ManyToOne 使用此标签建立多对一关联，此属性在“多”方使用注解在我们的“一”方属性上
     * @cascade 指定级联操作，以数组方式指定，如果只有一个，可以省略“{}”
     * @fetch 定义抓取策略
     * @optional 定义是否为必需属性，如果为必需（false），但在持久化时user = null,则会持久化失败
     * @targetEntity 目标关联对象，默认为被注解属性所在类
     */
    @ManyToOne(cascade = CascadeType.ALL,fetch = FetchType.LAZY)
    @JoinColumn(name = "user_id",unique = false,updatable = true)
    private User user;


    public Integer getId() {
        return id;
    }
    public void setId(Integer id) {
        this.id = id;
    }
    public String getContent() {
        return content;
    }
    public void setContent(String content) {
        this.content = content;
    }
    public User getUser() {
        return user;
    }
    public void setUser(User user) {
        this.user = user;
    }






}

映射关系确立好，开始编写我们的测试文件：

package com.chenhao.hibernate.Hibernate;

import java.util.HashSet;
import java.util.Set;

import org.hibernate.Session;
import org.hibernate.SessionFactory;
import org.hibernate.Transaction;
import org.junit.After;
import org.junit.Before;
import org.junit.BeforeClass;
import org.junit.Test;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.ClassPathXmlApplicationContext;

import com.chenhao.hibernate.model.Article;
import com.chenhao.hibernate.model.User;

public class ArticleTest {


        private static ApplicationContext ac;
        private static SessionFactory sessionFactory;
        private Session session;
        private Transaction transaction;


        @BeforeClass//在测试类初始化时调用此方法，完成静态对象的初始化
        public static void before(){

            ac = new ClassPathXmlApplicationContext("spring-datasource.xml");
            sessionFactory = (SessionFactory) ac.getBean("sessionFactory");

        }

        @Before//每一个被注解Test方法在调用前都会调用此方法一次
        public void setup(){//建立针对我们当前测试方法的的会话和事务
            session = sessionFactory.openSession();
            transaction = session.beginTransaction();

        }

        @Test
        public void test3(){
            User user = new User();
            user.setName("oneObject");
            Set<Article> articles = new HashSet<Article>();
            for(int i = 0 ; i < 3;i ++){
                Article article = new Article();
                article.setContent("moreContent" + i) ;
                articles.add(article);
            }
            user.setArticles(articles);//建立关联关系
            session.save(user);
        }

        @After//每一个被注解Test方法在调用后都会调用此方法一次
        public void teardown(){

            transaction.commit();//提交事务，主要为了防止在测试中已提交事务，这里又重复提交
            session.clear();
            session.close();
            sessionFactory.close();//
        }
        @After//在类销毁时调用一次
        public void after(){

        }

}

然后我们再运行测试方法：会看到：

Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
Hibernate: select next_val as id_val from hibernate_sequence for update
Hibernate: update hibernate_sequence set next_val= ? where next_val=?
Hibernate: insert into t_user1 (name, id) values (?, ?)
Hibernate: insert into t_article1 (content, user_id, id) values (?, ?, ?)
Hibernate: insert into t_article1 (content, user_id, id) values (?, ?, ?)
Hibernate: insert into t_article1 (content, user_id, id) values (?, ?, ?)
Hibernate: update t_article1 set user_id=? where id=?
Hibernate: update t_article1 set user_id=? where id=?
Hibernate: update t_article1 set user_id=? where id=?

此外，我们可以通过测试尝试从user中获取article对象来进一步验证：

User user = (User) session.get(User.class, 1);
System.out.println("获取用户对应的文章数据："+user.getArticles());

打印结果：获取用户对应的文章数据：[]
这是因为我们的关联信息是由多方维护的(user_id)，我们想要真正完成两者，必须从主维护方：article下手
运行以下测试代码：

User user = new User();
user.setName("oneObject1");
for(int i = 0 ; i < 3;i ++){
    Article article = new Article();
    article.setContent("moreContent1" + i) ;
    article.setUser(user);//有article来建立关联关系
    session.save(article);//持久化
}

得到打印结果：

Hibernate: insert into t_user1 (name) values (?) 
Hibernate: insert into t_article1 (content, user_id) values (?, ?) 
Hibernate: insert into t_article1 (content, user_id) values (?, ?) 
Hibernate: insert into t_article1 (content, user_id) values (?, ?) 

DEBUG: org.hibernate.internal.util.EntityPrinter - com.zeng.model.Article{content=moreContent10, id=4, user=com.zeng.model.User#2} 
DEBUG: org.hibernate.internal.util.EntityPrinter - com.zeng.model.Article{content=moreContent12, id=6, user=com.zeng.model.User#2} 
DEBUG: org.hibernate.internal.util.EntityPrinter - com.zeng.model.Article{content=moreContent11, id=5, user=com.zeng.model.User#2} 
DEBUG: org.hibernate.internal.util.EntityPrinter - com.zeng.model.User{id=2, articles=null, name=oneObject1} 

再查看数据库： 
MySQL> select * from t_article1; 
+—-+—————+———+ 
| id | content | user_id | 
+—-+—————+———+ 
| 1 | moreContent2 | NULL |——————上次操作遗留 
| 2 | moreContent1 | NULL |——————上次操作遗留 
| 3 | moreContent0 | NULL |——————上次操作遗留 
| 4 | moreContent10 | 2 | 
| 5 | moreContent11 | 2 | 
| 6 | moreContent12 | 2 | 
+—-+—————+———+ 
6 rows in set (0.00 sec)

从sql语句和蓝色DEBUG、数据库记录我们能够看出，这才是最优雅的添加关联操作，既没有多余的update语句，同时完成了数据库关联关系的建立。