[nhibernate-issues] [NHJIRA] Updated: (NH-2661) NHibernate cannot handle SQL Server TIME columns when built with the .NET 4 framework

[Neal G. (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neal Groothuis updated NH-2661:
-------------------------------

    Attachment: NHibernate.Test-2661.zip

Unit test illustrating the problem.  This includes a custom TimeType which works around the problem in NH-2660.

> NHibernate cannot handle SQL Server TIME columns when built with the .NET 4 framework
> -------------------------------------------------------------------------------------
>
>                 Key: NH-2661
>                 URL: http://216.121.112.228/browse/NH-2661
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.1.GA, 2.1.2.GA, 3.0.0.Alpha1, 3.0.0.Alpha2, 3.0.0.Alpha3, 3.0.0.Beta1, 3.0.0.Beta2, 3.0.0.CR1, 3.0.0.GA, 3.1.0
>            Reporter: Neal Groothuis
>            Priority: Minor
>         Attachments: NHibernate.Test-2661.zip
>
>
> In .NET 4, setting a SqlParameter's DbType to Time does not work; it will be set to DateTime instead.  (http://msdn.microsoft.com/en-us/library/system.data.dbtype%28v=VS.100%29.aspx , c.f. http://msdn.microsoft.com/en-us/library/system.data.dbtype%28v=VS.90%29.aspx ).  To set a SqlParameter's DbType to Time, you actually have to set the SqlDbType property to SqlDbType.Time.  
> Unfortunately, this renders NHibernate unable to access TIME columns in the database if being used in .NET 4.0.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira