Hi,

I have a named query that used to work before 3.1. Here is the named query:

After going to 3.1, I get an error that basically said it cannot set the value for parameter, whiteLightRawValue. When I checked the debug statement, it is trying to set the value as a DoubleType. However, the field, whiteLightRawValue, is actually a Float type.

Hibernate version: 3.1
Database and version: MySQL 5.0.16

Here is the code to set the parameter:


Here is the snippet of the mapping between the database column and the Java field:

If anyone need the entire mapping file or persistent class, I can provide them but they are rather long. Basically, the MySQL column for WhiteLightRawValue is defined as a float in MySQL and the mapped field in the persisent class is a Java Float.

One last thing, when I changed the code to explicitly set the parameter as a Float type (see below), then it works. But as I stated before, this worked before 3.1, so I am guessing that's a bug in 3.1?



Thanks,
Ben

hibernate 3.1 have stronger type checking thane previous versions - you have to set
same type in property and parameter
I don't sure is it mistake - i like parameter conversion for simpler types (number, string etc),too

Yes there was a change in the way unspecified parameter types are guessed in 3.1. In 3.1, the query parser attempts to guess an expected type for any parameters it encounters based on the context of the tree around the parameter. This is all new code, so it is likely I made it a little too restrictive.

The old code was solely based on the java type of the passed parameter value to bind, which in more cases than not resulted in bad choices.

Either post the syntax tree from the parser for that query, or open an enhancement request in JIRA with a runnable case using that query.

FWIW, the new code should work with your query if you change around the structure of the where clause expressions a bit:

The "expected type guessing" here would be based on the left and right hand sides of the '<' and '>' comparisons. In the modified query, that should correctly resolve to float since scan.whiteLightRawValue is mapped as float; thus :whiteLightRawValue would be expected to be of type float. I would guess that the literal '.0001' is not being typed correctly by the parser which then is causing the issue you see.

Or, explicitly set the type as you found...

Or actually, all you really need to do is to tell the parser that these literals should be treated as floats:

Steve, please add this with a note to the migration guide. Thanks

err, hold on. there is currently a bug in how float-literals are sent to the database (they go "as-is", meaning .0001f gets sent to the databse). I'll fix that for 3.1.1.


But it'll fix your parameter binding thing ;)