Projectable.uniqueResult() semantics

[cowwoc]

It's not clear what happens if Projectable.uniqueResult() is invoked on a query that returns multiple results.

[Timo Westkämper (timo-westkamper)]

Is this ok : for multiple results only the first one is returned

The details are implementation specific

[cowwoc (gili)]

Timo,

The text you mentioned is okay but I am somewhat concerned about the method name. Coming from JPA I am somewhat unused to the method throwing an exception if multiple matches are found. I guess I could push this integrity-checking into the database using the UNIQUE keyword, but then I'm strongly in favor of renaming the method to something along the lines of firstResult(). The current method name implies that the result is unique, which is not necessarily true.

[cowwoc (gili)]

"somewhat unused to the method throwing an exception" should read "somewhat used to the method throwing an exception"

[Timo Westkämper (timo-westkamper)]

firstResult() also somewhat implies that the result is ordered, which it is not necessarily.

Maybe I should instead always throw an Exception if more than one result is found. Then this would be consistent. For Hibernate and JPA this would already be the case and could easily be applied to the other modules.

[cowwoc (gili)]

I would be fine with that.

[Timo Westkämper (timo-westkamper)]

Released in 2.1.2