[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1855?page=all ]
Steve Ebersole resolved HHH-1855:
---------------------------------
Resolution: Fixed
Done.
For boolean literals, the old code always routed "resolution" of the literals through Dialect.toBooleanValueString(). The new code utilizes the ExpectedTypeAwareNode infrastructure to inject an expected type into the BooleanLiteralNode, usually based on the type of the property against which the bool-literal is being compared.
For parameters, a drastic change was to make setBoolean() prefer the expected type. This is different than all the other "typed param setters", in that all others prefer the explicit type over the expected type.
> booleans not properly handled in assignment clause of UPDATE statements
> -----------------------------------------------------------------------
>
> Key: HHH-1855
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1855
> Project: Hibernate3
> Type: Bug
> Components: query-hql
> Reporter: Steve Ebersole
> Assignee: Steve Ebersole
> Fix For: 3.2.0
>
>
> booleans, either as literals or as parameters, are not properly handled when encountered in the assignment (SET) clause of UPDATE statements. Specifically, they are not treated as the "correct" type.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
