System.TimeSpan is what .Net offers to match a Sql.Time. There is no real discussion about the 1657 since nobody showed interest. The reason of these changes are the types introduces on .Net 2 Sp1
On Wed, Mar 25, 2009 at 1:22 PM, Oskar Berggren <oskar.bergg...@gmail.com>wrote: > To me it seems quite weird that a CLR TimeSpan by default be stored as a > sql TIME, since they are conceptually different things. And with the wildly > different ranges there is as seen a practical difference too. > > I can find no real discussion on this change in NH-1657 and in the mail > archives, though it was mentiond on Feb 5th. What is the reasoning behind > this move? Has anyone actually requested this change? > > /Oskar > -- 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 nhusers@googlegroups.com To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
