[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3055?page=c...
]
Anthony Ogier commented on HHH-3055:
------------------------------------
Actually it doesn't seem to be enough ... finally I did like you, creating my own
dialect, extending org.hibernate.dialect.SQLServerDialect and including that code into the
constructor :
registerColumnType( Types.FLOAT, "real" );
But then, every Entity using java Float fields must map to a "real" type field
in the database. Moreover, if the database contains "float" fields, then one
must add a mapping to another java type ...
I'm not sure it's the good solution to handle SQL Server "real" type
into hibernate...
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