]
Emmanuel Bernard commented on HHH-2799:
---------------------------------------
It does not really make sense to define scale without a precision, does it?
I think it does not, that's the reason for the if in the Ejb3Column :)
Default Scale value doesn't right
---------------------------------
Key: HHH-2799
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2799
Project: Hibernate3
Issue Type: Bug
Components: metamodel
Affects Versions: 3.2.0.ga
Environment: Name and version of the database you are using:MySQL 5.0.37
Reporter: Bliznets Roman
Original Estimate: 2 hours
Remaining Estimate: 2 hours
In my Mapping documents:
...
<property name="goodsNumeric" lazy="false" insert="true"
update="true" not-null="false" unique="false"
type="java.math.BigInteger">
<column not-null="false" unique="false"
name="`goodsnumeric`" precision="5"/>
</property>
...
From MySQL documentation
In standard SQL, the syntax DECIMAL(M) is equivalent to DECIMAL(M,0).
But In log and in database scale=2, it's have to be exactly 0.
Debug level Hibernate log excerpt:
12484 [main] DEBUG org.hibernate.tool.hbm2ddl.SchemaUpdate - create table
`goodsitembasetype` (e_id bigint not null auto_increment, e_version integer not null,
`goodsnumeric` numeric(5,2), `grossweightquantity` numeric(19,6), `netweightquantity`
numeric(19,6), `invoicedcost` numeric(16,2), `customscost` numeric(16,2),
`statisticalcost` numeric(16,2), primary key (e_id))
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: