Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16986 ( https://hibernate.atlassian.net/browse/HHH-16986?atlOrigin=eyJpIjoiY2IyOT... ) Re: CoercionException caused by attempted coercion of query param to entity field type ( https://hibernate.atlassian.net/browse/HHH-16986?atlOrigin=eyJpIjoiY2IyOT... ) Right, that’s what I was alluding to when I said: though I was thinking more of the case of such an expression occurring in a where clause. But it’s really not as simple as you imagine, since we can have quite complex expressions involving parameters and functions and operators and allowing things like this would mean not type checking the whole expression as soon as the expression involves a parameter and a numeric operator. That’s a bit nasty. And yes, of course we could make it work in a piecemeal way for some special cases. But that’s a bad way to design languages. I much prefer bright-line rules about what is allowed and what is disallowed. Otherwise you end up with Perl. So it’s simply unclear whether this is something we should even try to fix. (I need to talk it over with Steve.) Right, that’s exactly what it does: it infers the parameter type from the other operand. This is the best it can do in general. What you’re asking the query compiler to do is an implicit numeric type promotion to a type it has no way of knowing. That’s asking for rather a lot. In general, it’s asking for the impossible. Now, one option which I’ve toyed with a bit is allowing the type of parameters to be declared explicitly, something like: select test.intField * BigDecimal?1 select test.intField * BigDecimal: name or: select test.intField * (?1 as BigDecimal) select test.intField * (: name as BigDecimal) or whatever. This would solve the problem completely. In the meantime, I don’t think the obvious workaround is that terrible: select cast(test.intField as BigDecimal) * ?1 This is just barely more verbose than the proposed new syntax (one extra token). Implicit type promotions can always be rewritten as explicit casts, so this workaround always works. ( https://hibernate.atlassian.net/browse/HHH-16986#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16986#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100233- sha1:f5b6255 )