[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3055?page=c...
]
Guillaume Grussenmeyer commented on HHH-3055:
---------------------------------------------
Hi Anthony,
concerning the fact that "every Entity using java Float fields must map to a
"real" type field in the database", that's precisely what we're
trying to achieve: not doing so will led to precision loss during database data reading
(trying to stuff a double-precision data (db level) into a single-precision one (java
level)).
If your database contains "float" fields, they should be mapped as
"double" in Java. In that case, Hibernate will use JDBC DOUBLE type (as per
org.hibernate.type.DoubleType), so there is no need to add another mapping.
Another solution is not to use any float Java fields and use doubles instead.
Incorrect type of SQLServer column for Java 'float' field
---------------------------------------------------------
Key: HHH-3055
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3055
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.1
Environment: Hibernate Annotations 3.3.0.GA
Hibernate EntityManager 3.3.1.GA
Hibernate 3.2.1
Microsoft SQL Server, version: 9.00.3042
Microsoft SQL Server 2005 JDBC Driver, version: 1.1.1501.101
Reporter: Guillaume Grussenmeyer
When mapping a Java field of type 'float' to a SQLServer table, the corresponding
database column is created with type 'float', which is not correct as SQL Server
floats are double precision, while Java floats are simple precision.
The corresponding column should be created with type "real".
--
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