Thread: [nhibernate-issues] [NHJIRA] Created: (NH-2660) Db.Time types are being set as DateTime

Brought to you by: ayenderahien, bahusoid, fabiomaulo, fdelaporte, and 5 others

nhibernate-issues

[nhibernate-issues] [NHJIRA] Created: (NH-2660) Db.Time types are being set as DateTime

From: Neal G. (JIRA) <nh...@gm...> - 2011-04-20 16:46:31

Db.Time types are being set as DateTime
---------------------------------------

                 Key: NH-2660
                 URL: http://216.121.112.228/browse/NH-2660
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.1.0, 3.0.0.GA, 3.0.0.CR1, 3.0.0.Beta2, 3.0.0.Beta1, 3.0.0.Alpha3, 3.0.0.Alpha2, 3.0.0.Alpha1, 2.1.2.GA, 2.1.1.GA
            Reporter: Neal Groothuis
            Priority: Minor


NHibernate.Type.TimeAsTimeSpanType and NHibernate.Type.TimeType add DateTime parameters to the commands passed to their Set() methods, but per this MSDN article: http://msdn.microsoft.com/en-us/library/cc716729.aspx , the .NET datatype that should be used for DbType.Time fields is TimeSpan.  At least when trying to update TIME columns with SQL Server 2008, this causes an error.  

I believe that this can be fairly easily corrected by having the Set() methods save TimeSpans rather than DateTimes to the parameter list.

-- 
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

[nhibernate-issues] [NHJIRA] Updated: (NH-2660) Db.Time types are being set as DateTime

From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-20 17:40:33

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

Fabio Maulo updated NH-2660:
----------------------------

    Affects Version/s:     (was: 3.0.0.GA)
                           (was: 3.0.0.CR1)
                           (was: 3.0.0.Beta2)
                           (was: 3.0.0.Beta1)
                           (was: 3.0.0.Alpha3)
                           (was: 3.0.0.Alpha2)
                           (was: 2.1.2.GA)
                           (was: 2.1.1.GA)
                           (was: 3.0.0.Alpha1)

> Db.Time types are being set as DateTime
> ---------------------------------------
>
>                 Key: NH-2660
>                 URL: http://216.121.112.228/browse/NH-2660
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Neal Groothuis
>            Priority: Minor
>
> NHibernate.Type.TimeAsTimeSpanType and NHibernate.Type.TimeType add DateTime parameters to the commands passed to their Set() methods, but per this MSDN article: http://msdn.microsoft.com/en-us/library/cc716729.aspx , the .NET datatype that should be used for DbType.Time fields is TimeSpan.  At least when trying to update TIME columns with SQL Server 2008, this causes an error.  
> I believe that this can be fairly easily corrected by having the Set() methods save TimeSpans rather than DateTimes to the parameter list.

-- 
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

[nhibernate-issues] [NHJIRA] Updated: (NH-2660) Db.Time types are being set as DateTime

From: Neal G. (JIRA) <nh...@gm...> - 2011-04-20 18:08:32

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

Neal Groothuis updated NH-2660:
-------------------------------

    Attachment: NHibernate.Test.zip

Test case illustrating the problem.

> Db.Time types are being set as DateTime
> ---------------------------------------
>
>                 Key: NH-2660
>                 URL: http://216.121.112.228/browse/NH-2660
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Neal Groothuis
>            Priority: Minor
>         Attachments: NHibernate.Test.zip
>
>
> NHibernate.Type.TimeAsTimeSpanType and NHibernate.Type.TimeType add DateTime parameters to the commands passed to their Set() methods, but per this MSDN article: http://msdn.microsoft.com/en-us/library/cc716729.aspx , the .NET datatype that should be used for DbType.Time fields is TimeSpan.  At least when trying to update TIME columns with SQL Server 2008, this causes an error.  
> I believe that this can be fairly easily corrected by having the Set() methods save TimeSpans rather than DateTimes to the parameter list.

-- 
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

[nhibernate-issues] [NHJIRA] Closed: (NH-2660) Db.Time types are being set as DateTime

From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-24 20:58:50

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

Fabio Maulo closed NH-2660.
---------------------------

    Resolution: Won't Fix

Don't worry for the "won't fix"... I'm on the workaround of the Ms bug.
I'll introduce two new NH's types.
- DateTimeToTimeSpanType 
- TimeSpanType (with a breaking change for the old one who will renamed to TimeSpanAsInte64Type)

> Db.Time types are being set as DateTime
> ---------------------------------------
>
>                 Key: NH-2660
>                 URL: http://216.121.112.228/browse/NH-2660
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Neal Groothuis
>            Priority: Minor
>         Attachments: NHibernate.Test.zip
>
>
> NHibernate.Type.TimeAsTimeSpanType and NHibernate.Type.TimeType add DateTime parameters to the commands passed to their Set() methods, but per this MSDN article: http://msdn.microsoft.com/en-us/library/cc716729.aspx , the .NET datatype that should be used for DbType.Time fields is TimeSpan.  At least when trying to update TIME columns with SQL Server 2008, this causes an error.  
> I believe that this can be fairly easily corrected by having the Set() methods save TimeSpans rather than DateTimes to the parameter list.

-- 
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