You can set the Projection for this like: .setProjection(Projections.property(“firstname”)) With this you can only get the firstname in return. I have found another link on stack with the same scenario. Hope this will also help How to use hibernate criteria to return only one element of an object instead the entire object?
We are deprecating the Criteria API in lieu of JPA extension support. Consider this: CriteriaBuilder cb = entityManager.getCriteriaBuilder(); HibernateCriteria hc = cb.unwrap( HibernateCriteria.class ); … query.where( hc.someAwesomeThing( … ) ); List<SomeEntity> entities = entityManager.createQuery( query ).getResultList(); Contrary to comments, we do intend to continue to deliver Hibernate-specific features, but we want to introduce those through … Read more
Hibernate queries are case sensitive with property names (because they end up relying on getter/setter methods on the @Entity). Make sure you refer to the property as fileName in the Criteria query, not filename. Specifically, Hibernate will call the getter method of the filename property when executing that Criteria query, so it will look for … Read more
Please refer to this for the example .The main point is to use the groupProperty() , and the related aggregate functions provided by the Projections class. For example : SELECT column_name, max(column_name) , min (column_name) , count(column_name) FROM table_name WHERE column_name > xxxxx GROUP BY column_name Its equivalent criteria object is : List result = … Read more
While similar names, the usage is different. I. Projections.distinct(Projections.property(“id”)); this statement would be translated into SQL Statement. It will be passed to DB Engine and executed as a SQL DISTINCT. See: 17.9. Projections, aggregation and grouping so e.g. this example: List results = session.createCriteria(Cat.class) .setProjection( Projections.projectionList() .add( Projections.distinct(Projections.property(“id”)) ) ) .list(); would seems like: SELECT … Read more
They’re not mutually exclusive, you can use both at the same time. Projections are generally used in the context of some Criteria. To put it simple, Hibernate Projections are used in order to query only a subset of the attributes of an entity or group of entities you’re querying with Criteria. You can also use … Read more
Use Projections to specify which columns you would like to return. Example SQL Query SELECT user.id, user.name FROM user; Hibernate Alternative Criteria cr = session.createCriteria(User.class) .setProjection(Projections.projectionList() .add(Projections.property(“id”), “id”) .add(Projections.property(“Name”), “Name”)) .setResultTransformer(Transformers.aliasToBean(User.class)); List<User> list = cr.list();
It may seem a little awkward at first, but it is type-safe. Building queries from strings isn’t, so you notice errors at runtime instead of at compile time. You can make the queries more readable by using indentations or taking each step separately, instead of writing an entire WHERE clause in a single line. To … Read more
I’m the guy who wrote the Hibernate 3 query translator back in 2004, so I know something about how it works. Criteria, in theory should have less overhead than an HQL query (except for named queries, which I’ll get to). This is because Criteria doesn’t need to parse anything. HQL queries are parsed with an … Read more
think works Criteria criteria = getSession().createCriteria(clazz); Criterion rest1= Restrictions.and(Restrictions.eq(A, “X”), Restrictions.in(“B”, Arrays.asList(“X”,Y))); Criterion rest2= Restrictions.and(Restrictions.eq(A, “Y”), Restrictions.eq(B, “Z”)); criteria.add(Restrictions.or(rest1, rest2));