Any solution to this? I see plenty of hibernate JIRA issues etc, but no
solution.
Turning off schema validation will work, but we'd much prefer it on.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4102856#4102856
Reply to the post :
have you tried BigInteger? i just checked the hibernate reference documentation
version: 3.2 cr1 and it mentions:
big_decimal, big_integer: Type mappings from java.math.BigDecimal and
java.math.BigInteger to NUMERIC (or Oracle NUMBER).
View the original post :
you can also map oracle Number to BigDecimal. i have some Number with precision
points and am mapping them to BigDecimal in my POJOs. they work fine.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034508#4034508
Reply to the post :
The problem I am facing is hibernate validator. If I turn off validator, there
is no problem for the mapping at run time.
I tried big_decimal. It could not pass the hibernate validator. Looks like the
jdbc driver returns decimal type but the hibernate expected numeric. They are
really the same
have you tried using Long in your code to map it to a Oracle Number data type?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034060#4034060
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034060
We need either BigDecimal or double (not integer). Long does not make sense to
us.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034095#4034095
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034095
