Querydsl

JPA : uniqueResult throws NoResultException instead of returning null

Bug #624727 reported by Timo Westkämper
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.

Revision history for this message
Timo Westkämper (timo-westkamper) wrote :

Fixed by catching the Exception and returning null instead

Changed in querydsl:
status: New → Fix Committed
Timo Westkämper (timo-westkamper)
summary: - uniqueResult throws NoResultException instead of returning null
+ JPA : uniqueResult throws NoResultException instead of returning null
Revision history for this message
Timo Westkämper (timo-westkamper) wrote :

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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.