首先,Criteria和DetachedCriteria不存在父子关系。但是,它们有一个共同的父接口CriteriaSpecification。
Criteria
jdk的帮助文档中是这样介绍Criteria的:
Criteria is a simplified API for retrieving entities by composing Criterion objects. This is a very convenient approach for functionality like "search" screens where there is a variable number of conditions to be placed upon the result set.
The Session is a factory for Criteria. Criterion instances are usually obtained via the factory methods on Restrictions
大致意思是:
Criteria是一个简单的API, 通过组合Criterion实例来检索实体。如果要在很多个条件下得到结果集,那么这是一个非常方便的方法 。
Session接口是创建Criteria的工厂。Criterion实例通常通过Restrictions的工厂方法得到(关于Session的介绍可看其他博主的文章……)。示例:
Criteria c=session.createCriteria(Cat.class);
c=c.add(Restricions.like("name","%luc%")).add(Restrictions.like("name","%ll%"));
List cats=c.list();
DetachedCriteria
jdk的帮助文档关于DetachedCriteria的介绍:
Some applications need to create criteria queries in "detached mode", where the Hibernate session is not available. This class may be instantiated anywhere, and then a Criteria may be obtained by passing a session to getExecutableCriteria(). All methods have the same semantics and behavior as the corresponding methods of the Criteria interface.
大致意思:
一些应用在hibernamte session无效的情况下需要在分离模式下创建criteria查询条件。DetachedCriteria可以在任何地方实例化,然后通过getExecutableCriteria()方法并传递session参数获得Criteria对象。DetachedCriteria中的所有方法和Criteria接口中的方法有着相同的语义和行为。
也就是说,DetatchedCriteria对象不需要依靠session来创建。
1、实例化DetachedCriteria对象:
DetachedCriteria dc=DetachedCriteria.forClass(Cat.class)
2、DetachedCriteria对象转换为Criteria对象:
Criteria c=detachedCriteria.getExecutableCriteria(session)
DetachedCriteria与Criteria相比有什么好处呢?好处就是它的创建不需要依靠session。为什么要有转换成Criteria的方法?因为如果仅仅是detachedCriteria对象是无法与数据库建立联系的,因为它不存在与session中。