JPA : uniqueResult throws NoResultException instead of returning null

Bug #624727 reported by Timo Westkämper on 2010-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Querydsl
Fix Released
Undecided
Unassigned

Bug Description

According to com.mysema.query.Projectable#uniqueResult docs it should return null in case of "empty result", but for JPA Hibernate implementation it instead throws JPA specific exception.

Fixed by catching the Exception and returning null instead

Changed in querydsl:
status: New → Fix Committed
summary: - uniqueResult throws NoResultException instead of returning null
+ JPA : uniqueResult throws NoResultException instead of returning null

Released in 1.9.2

Changed in querydsl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers