Heibernate学习

Hibernate 映射类型

映射类型

当你准备一个 Hibernate 映射文件时，我们已经看到你把 Java 数据类型映射到了 RDBMS 数据格式。在映射文件中已经声明被使用的 types 不是 Java 数据类型；它们也不是 SQL 数据库类型。这种类型被称为 Hibernate 映射类型，可以从 Java 翻译成 SQL，反之亦然。

在这一章中列举出所有的基础，日期和时间，大型数据对象，和其它内嵌的映射数据类型。

原始类型

日期和时间类型

二进制和大型数据对象

JDK 相关类型

haibernate Mapping.hbm.xml 配置

<?xml version="1.0"?>
<!--
  ~ Hibernate, Relational Persistence for Idiomatic Java
  ~
  ~ License: GNU Lesser General Public License (LGPL), version 2.1 or later.
  ~ See the lgpl.txt file in the root directory or <http://www.gnu.org/licenses/lgpl-2.1.html>.
  -->
<!DOCTYPE hibernate-mapping PUBLIC
    "-//Hibernate/Hibernate Mapping DTD 3.0//EN"
    "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd">

<!--
    This mapping demonstrates the use of Hibernate with all-handwritten SQL!
     
    NOTE: this version is for SQLServer
-->
<hibernate-mapping package="com.hx.entity" default-access="field">

    <class name="Regions" table="regions">
        <id name="regionId" column="region_id">
            <generator class="native"/>
        </id>
        <set name="countries" table="countries"  inverse="true"><!--设置外键的表-->
            <key>
                <column name="region_id" ></column><!--本表外键的字段-->
            </key>
            <one-to-many class="Countries"></one-to-many><!--外键的类型-->

        </set>


        <property name="regionName" column="region_name"/>
    </class>
    <class name="Jobs" table="jobs">
        <id name="jobId"  column="Job_id">
            <generator class="native"></generator>
        </id>
        <property name="jobTitle" column="job_title"></property>
        <property name="maxSalary" column="max_salary"></property>
        <property name="minSalary" column="min_salary"></property>
    </class>
    <class name="Cups" table="cups">
        <id name="CupId" column="cup_Id" >
            <generator  class="native"/>
        </id>

        <property name="CupName"  column="Cup_Name"/>
    </class>
    <class name="Countries" table="countries">
        <id name="countryId" column="country_id">
            <generator class="native"></generator>
        </id>
        <property name="countryName" column="country_name"></property>
        <property name="regionId" column="region_id"></property>

        <many-to-one name="regions" class="Regions" column="region_Id" entity-name="Regions" ></many-to-one>
    </class>

    <!--
    <class name="Person" table="PERSON">
        <id name="id" unsaved-value="0" column="PERID">
            <generator class="increment"/>
        </id>
        <property name="name" not-null="true" column="NAME"/>
        <loader query-ref="person"/>
        <sql-insert>INSERT INTO PERSON (NAME, PERID) VALUES ( UPPER(?), ? )</sql-insert>
        <sql-update>UPDATE PERSON SET NAME=UPPER(?) WHERE PERID=?</sql-update>
        <sql-delete>DELETE FROM PERSON WHERE PERID=?</sql-delete>
    </class>
    
    <class name="Employment" table="EMPLOYMENT">
        <id name="employmentId" unsaved-value="0" column="EMPID">
            <generator class="increment"/>
        </id>
        <many-to-one name="employee" column="EMPLOYEE" not-null="true" update="false"/>
        <many-to-one name="employer" column="EMPLOYER" not-null="true" update="false"/>
        <property name="startDate" column="STARTDATE" not-null="true" update="false" insert="false"/>
        <property name="endDate" column="ENDDATE" insert="false"/>
        <property name="regionCode" column="REGIONCODE" update="false"/>
        <property name="salary" type="org.hibernate.test.sql.hand.MonetaryAmountUserType">
            <column name="VALUE" sql-type="float"/>
            <column name="CURRENCY"/>           
        </property>
        <loader query-ref="employment"/>
        <sql-insert>
            INSERT INTO EMPLOYMENT 
                (EMPLOYEE, EMPLOYER, STARTDATE, REGIONCODE, VALUE, CURRENCY, EMPID) 
                VALUES (?, ?, getdate(), UPPER(?), ?, ?, ?)
        </sql-insert>
        <sql-update>UPDATE EMPLOYMENT SET ENDDATE=?, VALUE=?, CURRENCY=? WHERE EMPID=?</sql-update> 
        <sql-delete>DELETE FROM EMPLOYMENT WHERE EMPID=?</sql-delete> 
    </class>

    <class name="TextHolder">
        <id name="id" column="id">
            <generator class="increment"/>
        </id>
        <property name="description" type="text" length="15000"/>
        <loader query-ref="textholder"/>
        <sql-insert>
            INSERT INTO TEXTHOLDER
            (DESCRIPTION, ID)
            VALUES (?, ?)
        </sql-insert>
        <sql-update>UPDATE TEXTHOLDER SET DESCRIPTION=? WHERE ID=?</sql-update>
        <sql-delete>DELETE FROM TEXTHOLDER WHERE ID=?</sql-delete>
    </class>

    <class name="ImageHolder">
        <id name="id" column="id">
            <generator class="increment"/>
        </id>
        <property name="photo" type="image" length="15000"/>
        <loader query-ref="imageholder"/>
        <sql-insert>
            INSERT INTO IMAGEHOLDER
            (PHOTO, ID)
            VALUES (?, ?)
        </sql-insert>
        <sql-update>UPDATE IMAGEHOLDER SET PHOTO=? WHERE ID=?</sql-update>
        <sql-delete>DELETE FROM IMAGEHOLDER WHERE ID=?</sql-delete>
    </class>

    <resultset name="org-emp-regionCode">
        <return-scalar column="regionCode" type="string"/>
        <return alias="org" class="Organization"/>
        <return-join alias="emp" property="org.employments"/>
    </resultset>

    <resultset name="org-emp-person">
        <return alias="org" class="Organization"/>
        <return-join alias="emp" property="org.employments"/>
        <return-join alias="pers" property="emp.employee"/>
    </resultset>
    
    <sql-query name="person">
        <return alias="p" class="Person" lock-mode="upgrade"/>
        SELECT NAME AS {p.name}, PERID AS {p.id} FROM PERSON WHERE PERID=? /*FOR UPDATE*/
    </sql-query>

    <sql-query name="organization">
        <return alias="org" class="Organization"/>
        <return-join alias="emp" property="org.employments"/>
        SELECT {org.*}, {emp.*}
        FROM ORGANIZATION org
            LEFT OUTER JOIN EMPLOYMENT emp ON org.ORGID = emp.EMPLOYER
        WHERE org.ORGID=?
    </sql-query>


    &lt;!&ndash;sql-query name="organization">
        <return alias="org" class="Organization"/>
        SELECT NAME AS {org.name}, ORGID AS {org.id} FROM ORGANIZATION
        WHERE ORGID=?
    </sql-query&ndash;&gt;
    
    <sql-query name="allOrganizationsWithEmployees" flush-mode="never">
        <return alias="org" class="Organization"/>
        SELECT DISTINCT org.NAME AS {org.name}, org.ORGID AS {org.id} 
        FROM ORGANIZATION org
        INNER JOIN EMPLOYMENT e ON e.EMPLOYER = org.ORGID
    </sql-query>
    
    
    

    
    <sql-query name="employment">
        <return alias="emp" class="Employment"/>
        SELECT EMPLOYEE AS {emp.employee}, EMPLOYER AS {emp.employer}, 
            STARTDATE AS {emp.startDate}, ENDDATE AS {emp.endDate},
            REGIONCODE as {emp.regionCode}, EMPID AS {emp.id}
        FROM EMPLOYMENT
        WHERE EMPID = ?
    </sql-query>

    <sql-query name="organizationEmployments">
        <load-collection alias="empcol" role="Organization.employments"/>
        SELECT {empcol.*}
        FROM EMPLOYMENT empcol
        WHERE EMPLOYER = :id
        ORDER BY STARTDATE ASC, EMPLOYEE ASC
    </sql-query>


    <sql-query name="organizationCurrentEmployments">
        <return alias="emp" class="Employment">         
            <return-property name="salary"> 
              &lt;!&ndash; as multi column properties are not supported via the
              {}-syntax, we need to provide an explicit column list for salary via <return-property> &ndash;&gt;
              <return-column name="`VALUE`"/>
              <return-column name="CURRENCY"/>          
            </return-property>
            &lt;!&ndash; Here we are remapping endDate. Notice that we can still use {emp.endDate} in the SQL. &ndash;&gt;
            <return-property name="endDate" column="myEndDate"/>
        </return>
        <synchronize table="EMPLOYMENT"/>
        SELECT EMPLOYEE AS {emp.employee}, EMPLOYER AS {emp.employer}, 
            STARTDATE AS {emp.startDate}, ENDDATE AS {emp.endDate},
            REGIONCODE as {emp.regionCode}, EMPID AS {emp.id}, VALUE, CURRENCY
        FROM EMPLOYMENT
        WHERE EMPLOYER = :id AND ENDDATE IS NULL
        ORDER BY STARTDATE ASC
    </sql-query>

    <sql-query name="simpleScalar" callable="true">
        <return-scalar column="name" type="string"/>
        <return-scalar column="`value`" type="long"/>
        { call simpleScalar(:number) }
    </sql-query>

    <sql-query name="paramhandling" callable="true">
        <return-scalar column="`value`" type="long"/>
        <return-scalar column="value2" type="long"/>
        { call paramHandling(?,?) }
    </sql-query>

    <sql-query name="paramhandling_mixed" callable="true">
        <return-scalar column="`value`" type="long" />
        <return-scalar column="value2" type="long" />
        { call paramHandling(?,:second) }
    </sql-query>
    
    <sql-query name="selectAllEmployments" callable="true">
        <return alias="" class="Employment">
            <return-property name="employee" column="EMPLOYEE"/>
            <return-property name="employer" column="EMPLOYER"/>            
            <return-property name="startDate" column="STARTDATE"/>
            <return-property name="endDate" column="ENDDATE"/>          
            <return-property name="regionCode" column="REGIONCODE"/>            
            <return-property name="id" column="EMPID"/>                     
            <return-property name="salary"> 
                &lt;!&ndash; as multi column properties are not supported via the
                {}-syntax, we need to provide an explicit column list for salary via <return-property> &ndash;&gt;
                <return-column name="`VALUE`"/>
                <return-column name="CURRENCY"/>            
            </return-property>
        </return>
        { call selectAllEmployments() }
    </sql-query>

    <sql-query name="textholder">
        <return alias="h" class="TextHolder" lock-mode="upgrade"/>
        SELECT ID AS {h.id}, DESCRIPTION AS {h.description} FROM TEXTHOLDER WHERE ID=? /*FOR UPDATE*/
    </sql-query>

    <sql-query name="imageholder">
        <return alias="h" class="ImageHolder" lock-mode="upgrade"/>
        SELECT ID AS {h.id}, PHOTO AS {h.photo} FROM IMAGEHOLDER WHERE ID=? /*FOR UPDATE*/
    </sql-query>
    
    <database-object>
        <create>
        CREATE PROCEDURE selectAllEmployments AS
            SELECT EMPLOYEE, EMPLOYER, STARTDATE, ENDDATE, 
            REGIONCODE, EMPID, VALUE, CURRENCY
            FROM EMPLOYMENT
        </create>
        <drop>
        DROP PROCEDURE selectAllEmployments
        </drop>
    </database-object>

    &lt;!&ndash; The following is a workaround for HHH-3685 so that SchemaExport &ndash;&gt;
    &lt;!&ndash; changes the transaction mode of selectAllEmployments to "chained" &ndash;&gt;
    <database-object>
        <create>
        sp_procxmode selectAllEmployments, 'chained'
        </create>
        &lt;!&ndash; no drop command corresponding to "sp_procxmode ..." &ndash;&gt;
        <drop/>
    </database-object>

    <database-object>
        <create>
        CREATE PROCEDURE paramHandling @j int, @i int AS
            SELECT @j as value, @i as value2
        </create>
        <drop>
        DROP PROCEDURE paramHandling
        </drop>
    </database-object>
    
    &lt;!&ndash; The following is a workaround for HHH-3685 so that SchemaExport &ndash;&gt;
    &lt;!&ndash; changes the transaction mode of paramHandling to "chained" &ndash;&gt;
    <database-object>
        <create>
        sp_procxmode paramHandling, 'chained'
        </create>
        &lt;!&ndash; no drop command corresponding to "sp_procxmode ..." &ndash;&gt;
    <drop/>
    </database-object>

    <database-object>
        <create>
        CREATE PROCEDURE simpleScalar @number int AS
            SELECT @number as value, 'getAll' as name
        </create>
        <drop>
        DROP PROCEDURE simpleScalar
        </drop>
    </database-object>
    
    &lt;!&ndash; The following is a workaround for HHH-3685 so that SchemaExport &ndash;&gt;
    &lt;!&ndash; changes the transaction mode of simpleScalar to "chained" &ndash;&gt;
    <database-object>
        <create>
        sp_procxmode simpleScalar, 'chained'
        </create>
        &lt;!&ndash; no drop command corresponding to "sp_procxmode ..." &ndash;&gt;
        <drop/>
    </database-object>
-->
</hibernate-mapping>

hibernate 注解的使用

Hibernate 检测到 @Id 注释字段并且认定它应该在运行时通过字段直接访问一个对象上的属性。如果你将 @Id 注释放在 getId() 方法中，你可以通过默认的 getter 和 setter 方法来访问属性。因此，所有其它注释也放在字段或是 getter 方法中，决定于选择的策略。下一节将解释上面的类中使用的注释。

@Entity 注释

EJB 3 标准的注释包含在 javax.persistence 包，所以我们第一步需要导入这个包。第二步我们对 Employee 类使用 @Entity 注释，标志着这个类为一个实体 bean，所以它必须含有一个没有参数的构造函数并且在可保护范围是可见的。

@Table 注释

@table 注释允许您明确表的详细信息保证实体在数据库中持续存在。

@table 注释提供了四个属性，允许您覆盖的表的名称，目录及其模式,在表中可以对列制定独特的约束。现在我们使用的是表名为 EMPLOYEE。

@Id 和 @GeneratedValue 注释

每一个实体 bean 都有一个主键，你在类中可以用 @Id 来进行注释。主键可以是一个字段或者是多个字段的组合，这取决于你的表的结构。

默认情况下，@Id 注释将自动确定最合适的主键生成策略，但是你可以通过使用 @GeneratedValue 注释来覆盖掉它。strategy 和 generator 这两个参数我不打算在这里讨论，所以我们只使用默认键生成策略。让 Hibernate 确定使用哪些生成器类型来使代码移植于不同的数据库之间。

@Column Annotation

@Column 注释用于指定某一列与某一个字段或是属性映射的细节信息。您可以使用下列注释的最常用的属性:

• name 属性允许显式地指定列的名称。
• length 属性为用于映射一个值，特别为一个字符串值的列的大小。
• nullable 属性允许当生成模式时，一个列可以被标记为非空。
• unique 属性允许列中只能含有唯一的内容

在java类中的使用

@Entity
public class Employees {
    @Id
    @Column(name = "EMPLOYEE_ID")
    private Integer employeeId;
    @Column(name = "FIRST_NAME")
    private String fristName;
    @Column(name = "LAST_NAME")
    private String lastName;
    @Column(name = "EMAIL")
    private String emall;
    @Column(name = "PHONE_NUMBER")
    private String phineNumber;
    @Column(name = "HIRE_DATE")
    private Timestamp hireDate;
    @ManyToOne(targetEntity = Jobs.class,fetch = FetchType.LAZY)//设置映射
    @JoinColumn(name = "job_id")
    private  Jobs job;
    @Column(name = "SALARY")
    private BigDecimal salary;
    @Column(name = "COMMISSION_PCT")
    private BigDecimal commissionPct;
    @Column(name = "MANAGER_ID")
    private Integer managerId;
    @Column(name = "DEPARTMENT_ID")
    private Integer departmentId;
    
    @Entity
public class Jobs {
    @Id
    @Column(name = "JOB_ID")
    private String jobId;
    @Column(name = "JOB_TITLE")
    private String jobTitle;
    @Column(name = "MIN_SALARY")
    private BigDecimal minSalary;
    @Column(name = "MAX_SALARY")
    private BigDecimal maxSalaty;

Hibernate 拦截器

由 北公爵无欢 创建， 最后一次修改 2016-08-12

拦截器

你已经学到，在 Hibernate 中，一个对象将被创建和保持。一旦对象已经被修改，它必须被保存到数据库里。这个过程持续直到下一次对象被需要，它将被从持久的存储中加载。

因此一个对象通过它生命周期中的不同阶段，并且 Interceptor 接口提供了在不同阶段能被调用来进行一些所需要的任务的方法。这些方法是从会话到应用程序的回调函数，允许应用程序检查或操作一个持续对象的属性，在它被保存，更新，删除或上传之前。以下是在 Interceptor 接口中可用的所有方法的列表。

Hibernate 拦截器给予了我们一个对象如何应用到应用程序和数据库的总控制。

如何使用拦截器？

为了创建一个拦截器你可以直接实现 Interceptor 类或者继承 EmptyInterceptor 类。以下是简单的使用 Hibernate 拦截器功能的步骤。

创建拦截器

我们将在例子中继承 EmptyInterceptor，当 Employee 对象被创建和更新时拦截器的方法将自动被调用。你可以根据你的需求实现更多的方法。

import java.io.Serializable;
import java.util.Date;
import java.util.Iterator;

import org.hibernate.EmptyInterceptor;
import org.hibernate.Transaction;
import org.hibernate.type.Type;

public class MyInterceptor extends EmptyInterceptor {
   private int updates;
   private int creates;
   private int loads;

   public void onDelete(Object entity,
                     Serializable id,
                     Object[] state,
                     String[] propertyNames,
                     Type[] types) {
       // do nothing
   }

   // This method is called when Employee object gets updated.
   public boolean onFlushDirty(Object entity,
                     Serializable id,
                     Object[] currentState,
                     Object[] previousState,
                     String[] propertyNames,
                     Type[] types) {
       if ( entity instanceof Employee ) {
          System.out.println("Update Operation");
          return true; 
       }
       return false;
   }
   public boolean onLoad(Object entity,
                    Serializable id,
                    Object[] state,
                    String[] propertyNames,
                    Type[] types) {
       // do nothing
       return true;
   }
   // This method is called when Employee object gets created.
   public boolean onSave(Object entity,
                    Serializable id,
                    Object[] state,
                    String[] propertyNames,
                    Type[] types) {
       if ( entity instanceof Employee ) {
          System.out.println("Create Operation");
          return true; 
       }
       return false;
   }
   //called before commit into database
   public void preFlush(Iterator iterator) {
      System.out.println("preFlush");
   }
   //called after committed into database
   public void postFlush(Iterator iterator) {
      System.out.println("postFlush");
   }
}

创建 POJO 类

现在让我们稍微修改我们的第一个例子，我们使用 EMPLOYEE 表单和 Employee 类：

public class Employee {
   private int id;
   private String firstName; 
   private String lastName;   
   private int salary;  

   public Employee() {}
   public Employee(String fname, String lname, int salary) {
      this.firstName = fname;
      this.lastName = lname;
      this.salary = salary;
   }
   public int getId() {
      return id;
   }
   public void setId( int id ) {
      this.id = id;
   }
   public String getFirstName() {
      return firstName;
   }
   public void setFirstName( String first_name ) {
      this.firstName = first_name;
   }
   public String getLastName() {
      return lastName;
   }
   public void setLastName( String last_name ) {
      this.lastName = last_name;
   }
   public int getSalary() {
      return salary;
   }
   public void setSalary( int salary ) {
      this.salary = salary;
   }
}

创建数据库表

第二步将是在你的数据库中创建表。一张表对应每个你提供持久性的对象。考虑以上的对象需要被存储和检索到以下的 RDBM 表中：

create table EMPLOYEE (
   id INT NOT NULL auto_increment,
   first_name VARCHAR(20) default NULL,
   last_name  VARCHAR(20) default NULL,
   salary     INT  default NULL,
   PRIMARY KEY (id)
);

创建 Mapping 配置文件

这个步骤是来创建一个指导 Hibernate 如何将定义的类或者多个类映射到数据库表单中的映射文件。

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE hibernate-mapping PUBLIC 
 "-//Hibernate/Hibernate Mapping DTD//EN"
 "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> 

<hibernate-mapping>
   <class name="Employee" table="EMPLOYEE">
      <meta attribute="class-description">
         This class contains the employee detail. 
      </meta>
      <id name="id" type="int" column="id">
         <generator class="native"/>
      </id>
      <property name="firstName" column="first_name" type="string"/>
      <property name="lastName" column="last_name" type="string"/>
      <property name="salary" column="salary" type="int"/>
   </class>
</hibernate-mapping>

创建 Application 类

最后，我们将用 main() 创建 application 类来运行应用程序。这里应该注意当创建 session 对象时我们使用 Interceptor 类作为参数。

import java.util.List; 
import java.util.Date;
import java.util.Iterator; 

import org.hibernate.HibernateException; 
import org.hibernate.Session; 
import org.hibernate.Transaction;
import org.hibernate.SessionFactory;
import org.hibernate.cfg.Configuration;

public class ManageEmployee {
   private static SessionFactory factory; 
   public static void main(String[] args) {
      try{
         factory = new Configuration().configure().buildSessionFactory();
      }catch (Throwable ex) { 
         System.err.println("Failed to create sessionFactory object." + ex);
         throw new ExceptionInInitializerError(ex); 
      }

      ManageEmployee ME = new ManageEmployee();

      /* Add few employee records in database */
      Integer empID1 = ME.addEmployee("Zara", "Ali", 1000);
      Integer empID2 = ME.addEmployee("Daisy", "Das", 5000);
      Integer empID3 = ME.addEmployee("John", "Paul", 10000);

      /* List down all the employees */
      ME.listEmployees();

      /* Update employee's records */
      ME.updateEmployee(empID1, 5000);

      /* Delete an employee from the database */
      ME.deleteEmployee(empID2);

      /* List down new list of the employees */
      ME.listEmployees();
   }
   /* Method to CREATE an employee in the database */
   public Integer addEmployee(String fname, String lname, int salary){
      Session session = factory.openSession( new MyInterceptor() );
      Transaction tx = null;
      Integer employeeID = null;
      try{
         tx = session.beginTransaction();
         Employee employee = new Employee(fname, lname, salary);
         employeeID = (Integer) session.save(employee); 
         tx.commit();
      }catch (HibernateException e) {
         if (tx!=null) tx.rollback();
         e.printStackTrace(); 
      }finally {
         session.close(); 
      }
      return employeeID;
   }
   /* Method to  READ all the employees */
   public void listEmployees( ){
      Session session = factory.openSession( new MyInterceptor() );
      Transaction tx = null;
      try{
         tx = session.beginTransaction();
         List employees = session.createQuery("FROM Employee").list(); 
         for (Iterator iterator = 
                           employees.iterator(); iterator.hasNext();){
            Employee employee = (Employee) iterator.next(); 
            System.out.print("First Name: " + employee.getFirstName()); 
            System.out.print("  Last Name: " + employee.getLastName()); 
            System.out.println("  Salary: " + employee.getSalary()); 
         }
         tx.commit();
      }catch (HibernateException e) {
         if (tx!=null) tx.rollback();
         e.printStackTrace(); 
      }finally {
         session.close(); 
      }
   }
   /* Method to UPDATE salary for an employee */
   public void updateEmployee(Integer EmployeeID, int salary ){
      Session session = factory.openSession( new MyInterceptor() );
      Transaction tx = null;
      try{
         tx = session.beginTransaction();
         Employee employee = 
                    (Employee)session.get(Employee.class, EmployeeID); 
         employee.setSalary( salary );
         session.update(employee); 
         tx.commit();
      }catch (HibernateException e) {
         if (tx!=null) tx.rollback();
         e.printStackTrace(); 
      }finally {
         session.close(); 
      }
   }
   /* Method to DELETE an employee from the records */
   public void deleteEmployee(Integer EmployeeID){
      Session session = factory.openSession( new MyInterceptor() );
      Transaction tx = null;
      try{
         tx = session.beginTransaction();
         Employee employee = 
                   (Employee)session.get(Employee.class, EmployeeID); 
         session.delete(employee); 
         tx.commit();
      }catch (HibernateException e) {
         if (tx!=null) tx.rollback();
         e.printStackTrace(); 
      }finally {
         session.close(); 
      }
   }
}

编译和执行

这里是编译和运行上面提及的应用程序的步骤。确保你已经在处理编译和执行前正确设置了 PATH 和 CLASSPATH。

• 创建在 configuration 章节中解释的 hibernate.cfg.xml 配置文件。
• 创建如上所示的 Employee.hbm.xml 映射文件。
• 创建如上所示的 Employee.java 源文件并编译。
• 创建如上所示的 MyInterceptor.java 源文件并编译。
• 创建如上所示的 ManageEmployee.java 源文件并编译。
• 执行 ManageEmployee 来运行程序。

你将得到以下结果，而且记录将在 EMPLOYEE 表单中被创建。

$java ManageEmployee
.......VARIOUS LOG MESSAGES WILL DISPLAY HERE........

Create Operation
preFlush
postFlush
Create Operation
preFlush
postFlush
Create Operation
preFlush
postFlush
First Name: Zara  Last Name: Ali  Salary: 1000
First Name: Daisy  Last Name: Das  Salary: 5000
First Name: John  Last Name: Paul  Salary: 10000
preFlush
postFlush
preFlush
Update Operation
postFlush
preFlush
postFlush
First Name: Zara  Last Name: Ali  Salary: 5000
First Name: John  Last Name: Paul  Salary: 10000
preFlush
postFlush

如果你检查你的 EMPLOYEE 表单，它应该有如下结果：

mysql> select * from EMPLOYEE;
+----+------------+-----------+--------+
| id | first_name | last_name | salary |
+----+------------+-----------+--------+
| 29 | Zara       | Ali       |   5000 |
| 31 | John       | Paul      |  10000 |
+----+------------+-----------+--------+
2 rows in set (0.00 sec
mysql>