hibernate关联映射（Hibernate关联映射）.docVIP

hibernate关联映射（Hibernate关联映射） First, the Association (the association and sharing the primary key foreign key associations only two) 1, sharing key Association Such as the subject by the teachers to teach, teachers have no problem, this problem can be completely determined by the teacher. The Java sample code is as follows: Publicclass {Course Private Long id; Private String name; Private Teacher teacher; / / omitting setter and getter method } Publicclass {Teacher Private Long id; Private String name; Private Course course; / / omitting setter and getter method } configuration file Teacher.hbm.xml ! -- cascade= all indicated that the Teacher CRUD object to the Course object -- cascade operation one-to-one name= course class= powerwind.bean.Course Cascade= all / Course.hbm.xml ! -- ID reference value for teacher attribute generation -- id name= Id type= java.lang.Long column= Id generator class= foreign param name= property teacher/param /generator /id ! -- teacher -- attribute reference one-to-one name= teacher class= powerwind.bean.Teacher Constrained= true / 2, the only foreign key The foreign key requires a definition of the key fields, such as the definition of a key course_id topic in the teacher table. configuration file Teacher.hbm.xml many-to-one name= course class= powerwind.bean.Course Column= course_id cascade= Save-update unique= true / If at the same time in Coure.hbm.xml with the following configuration for bidirectional association. one-to-one name= teacher class= powerwind.bean.Teacher Property-ref= course / 3, third More than two kinds of association in Hibernate is used. But I use another method to achieve, also found feasible. Test a bit, that there is no mistake. The idea is similar and the only foreign key associations, but the two table needs a foreign key, many-to-one used in the one-to-one configuration, both sides to use many-to-one. Course.hbm.xml many-to-one name= teacher class= powerwind.bean.Teacher Column= teacher_id unique= tr