[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-432?page=co...
]
Emmanuel Bernard commented on ANN-432:
--------------------------------------
ANN-423
So we can exclude all BigDecimal / BigInteger on range to make it consistent and let the
issue arise at developement time (at least unit testing)
or we can allow BigDecimal / BigInteger and raise an exception if we are above the limit
cases happends where min or max is unset, such an issue will arise most likely in
production only... I'm not a big fan of that.
@Range broken for BigDecimal/BigInteger
---------------------------------------
Key: ANN-432
URL:
http://opensource.atlassian.com/projects/hibernate/browse/ANN-432
Project: Hibernate Annotations
Type: Bug
Components: validator
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira