[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-3135) SQL Server Dialect maps BIGINT to NUMERIC(19,0)

[Jose Freire (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jose Freire updated HHH-3135:
-----------------------------

    Attachment: SQLServer2000Dialect.java

Uploaded SQLServer2000Dialect.java.

Maybe we could include this in the main distribution?

> SQL Server Dialect maps BIGINT to NUMERIC(19,0)
> -----------------------------------------------
>
>                 Key: HHH-3135
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3135
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.2.5
>         Environment: MS SQL Server
>            Reporter: Dominik Enkelmann
>            Priority: Trivial
>         Attachments: SQLServer2000Dialect.java
>
>
> The SQLServerDialect.java maps the Hibernate BIGINT type to a NUMERIC(19,0) colum. The result is, that all Long fields in persisten classes map to hibernate-bigints which generate numeric(19,0) database column. Longs are typically used for surrogate primary keys and should be implemented as native SQL BIGINTs where possible.
> SQL Server supports SQL BIGINT since version 2000. 
> There is a similar issue with the SQL BIT type that should be implemented as a native BIT column in SQL Server.
> A possible solution could be a pre-.SQL Server 2000 dialect and an updated SQL Server dialect.
> I filed a more detailed description with workaround in the user forum  http://forum.hibernate.org/viewtopic.php?p=2377674#2377674

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira