This is the use case of anyone who has a non-default mapping on any property of type byte, short, integer, long, float or double and uses the criteria API. That's not a common condition but certainly not specific to my application or even my class of application (or database). It is certainly a less surprising and more general case than the instances where values need to be inlined for query planning purposes.
I would not call working around irregular behavior 'being explicit'.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
This is the use case of anyone who has a non-default mapping on any property of type byte, short, integer, long, float or double and uses the criteria API. That's not a common condition but certainly not specific to my application or even my class of application (or database). It is certainly a less surprising and more general case than the instances where values need to be inlined for query planning purposes.
I would not call working around irregular behavior 'being explicit'.