Hi,

Are the following examples the only ways to hit the second-level cache?

1.

2.


Why doesn't the following code example hit my second-level cache (ehcache 1.3.0)?



The Criteria API should have all the information it needs to query the second-level cache, i.e. the identifier and the User class.




Hibernate version: 3.2.5ga

Mapping documents:
<class name="xxx.User" table="user" lazy="true">
<cache usage="nonstrict-read-write" />

<comment>Hibernate Mapping for User</comment>

<id name="id" column="id">
<generator class="native" />
</id>
<property name="alias" column="alias" />
<property name="createdTime" column="created_time" type="timestamp" />
<property name="email" column="email" />
</class>
Name and version of the database you are using: MySQL 5.0.42 (Linux CentOS)

I've come to the same conclusion myself - the criteria API never hits the second level query cache

By using <property name="hibernate.show_sql">true</property>, I can see whether a cache hit occurs.

Repeated calls of this code hit the query_cache
String queryString = "select s1 from PeriodNomination as s1 where s1.fieldGroupName = ? and s1.nominationDate = ? and s1.nominationHour = ? order by s1.nominationHour";
final List<PeriodNomination> list = getHibernateTemplate().find(queryString, new Object[] {fieldGroupName, nominationDate, nominationHour});
if (list.size() > 1) throw new RuntimeException();
return list.size()<=0?null:list.get(0);

Repeated calls of this code DON'T hit the query_cache
Criteria criteria = getSession().createCriteria(PeriodNomination.class);
criteria.add(Restrictions.eq("fieldGroupName", fieldGroupName));
criteria.add(Restrictions.eq("nominationDate", nominationDate));
criteria.add(Restrictions.eq("nominationHour", nominationHour));
return (PeriodNomination) criteria.uniqueResult();