Yes, the problem is with Sql 2005. Would be nice to see a patch for this dialect.
On Wed, Mar 25, 2009 at 1:20 PM, Roger Kratz <[email protected]>wrote: > Im using sql2005 dialect. (no explicit type in mapping file -> datetime > column) > > > > Whatever I persist… > > Assert.AreEqual(orgObj.MyTimeSpan, readObj.MyTimeSpan) > > …always fails due to the timespan have different number of days. They > differ with some ten thousand days ;) > > > > I can (try to) create a patch if you like? > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *Dario Quintana > *Sent:* den 25 mars 2009 17:14 > *To:* [email protected] > *Subject:* [nhusers] Re: TimeSpan >24h or <0h > > > > Roger, hi > > On Wed, Mar 25, 2009 at 1:03 PM, Roger Kratz <[email protected]> > wrote: > > IMHO – even with timespan between 0 and 24h, current impl give strange > results. As shown in attached jira tests, the timespan read has incorrect > days (even when timespan between 0 and 24h). Timespan persisted != timespan > read. Earlier nh tests only confirmed that hour, minutes and seconds > properties of the timespan are the same. > > BTW, what dialect are you using ? > When you're using TimeSpan, which match to an SqlServer Time type, you > can't talk about days, are completed ignored, you've to talk about hours, > minutes, seconds. > > I got passing VerifyDaysShouldBeZeroInSmallTimeSpan test. > > -- > Dario Quintana > http://darioquintana.com.ar > > > > > -- Dario Quintana http://darioquintana.com.ar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
