Hibernate中outer-join、lazy 、fetch join关键字的使用

1. outer-join关键字(many-to-one的情况)
outer-join关键字有3个值，分别是true,false,auto,默认是auto。
true: 表示使用外连接抓取关联的内容，这里的意思是当使用load(OrderLineItem.class,"id")时，Hibernate只生成一条SQL语句将OrderLineItem与他的父亲Order全部初始化。

select * from OrderLineItem o left join Order p on o.OrderId=p.OrderId  where o.OrderLineItem_Id=?

false: 表示不使用外连接抓取关联的内容，当load(OrderLineItem.class,"id")时，Hibernate生成两条SQL语句，一条查询OrderLineItem表，另一条查询Order表。这样的好处是可以设置延迟加载，此处要将Order类设置为lazy=true。

select * from OrderLineItem o where o.OrderLineItem_Id=?
select * from Order p where p.OrderId=?

auto: 具体是ture还是false看hibernate.cfg.xml中的配置

注意：如果使用HQL查询OrderLineItem，如 from OrderLineItem o where o.id='id'，总是不使用外部抓取，及outer-join失效。


2.  outer-join(集合)

由于集合可以设置lazy="true"，所以lazy与outer-join不能同时为true，当lazy="true"时，outer-join将一直是false，如果lazy="false"，则outer-join用法与1同。



3.  HQL语句会将POJO配置文件中的关联一并查询，即使在HQL语句中没有明确join。

 

4.  In HQL, the "fetch join" clause can be used for per-query specific outer join fetching. One important thing many people miss there, is that HQL queries will ignore the outer-join attribute you specified in your mapping. This makes it possible to configure the default loading behaviour of session.load() and session.get() and of objects loaded by navigating relationship. So if you specify and then do



MyObject obj = session.createQuery("from MyObject").uniqueResult();
obj.getMySet().iterator().next();



you will still have an additional query and no outer-join. So you must explicily request the outer-join fetching:

MyObject obj = session.createQuery("from MyObject mo left join fetch mo.mySet").uniqueResult();
obj.getMySet().iterator().next();



Another important thing to know is that you can only fetch one collection reference in a query. That means you can just use one fetch join. You can however fetch "one" references in addition, as this sample from the Hibernate Docs demonstrates:

from eg.Cat as cat
    inner join fetch cat.mate

    left join fetch cat.kittens


We have once considered lifting this limitation, but then decided against it, because using more than one fetch-join would be a bad idea generally: The generated ResultSet becomes huge and is a major performance loss.

So alltogether the "fetch join" clause is an important instrument Hibernate users should learn how to leverage, as it allows tuning the fetch behaviour of a certain use case.



5.  join fetch 与 join 的区别

如果HQL使用了连接，但是没有使用fetch关键字，则生成的SQL语句虽然有连接，但是并没有取连接表的数据，还是需要单独的sql取数据，也就是 select a, b, d...中没有连接表的字段。

6.  如果集合被声明为lazy=true，在HQL中如果显式的使用 join fetch 则延迟加载失效。



7.  在one-to-many的one端显式设置fecth="join"，则无论如何都采取预先抓取（生成一个SQl），延迟加载失效(生成两个SQL)。

8.  many-to-one的延迟加载是在配置文件的class标签设置lazy="true"，one-to-many和many-to-many的延迟加载是在set标签中设置lazy="true"。而one-to-one不只要在calss标签设置lazy="true"，而且要在one-to-one标签中设置constrained="true"。