And if so, under what circumstances?
Javadoc and JPA spec says nothing.
And if so, under what circumstances?
Javadoc and JPA spec says nothing.
If the specs said it could't happen, would you belive them? Given that your code could conceivably run against may different JPA implementations, would you trust every implementer to get it right?
No matter what, I would code defensively and check for null.
Now the big question: should we treat "null" and an empty List as synonymous? This is where the specs should help us, and don't.
My guess is that a null return (if indeed it could happen) would be equivalent to "I didn't understand the query" and empty list would be "yes, understood the query, but there were no records".
You perhaps have a code path (likely an exception) that deals with unparsable queries, I would tend to direct a null return down that path.
Hi,
You are right. JPA specification says nothing about it. But Java Persistence with Hibernate book says:
If the query result is empty, a null is returned
Hibernate JPA implementation (Entity Manager) return null when you call query.getResultList() with no result.
Contrary to Arthur's post, when I actually ran a query which no entities matched I got an empty list, not null. This is using Hibernate and is what I consider correct behaviour: an empty list is the correct answer when you ask for a collection of entities and there aren't any.
Of course, if you test the result set with Jakarta's CollectionUtils.isNotEmpty, you're covered either way.