On Wed, Mar 25, 2009 at 1:47 PM, Jay Chapman <[email protected]> wrote:
> I don't agree with this statement at all. Hasn't the System.TimeSpan > existed for a much longer time than Sql.Time? So how could it possibly be > an offer to support Sql.Time when that didn't exist? > Which one? I don't know what you mean with this, but, we added a new features, we didn't remove one. > I can say for sure that I have used TimeSpan in the past for tracking > things like the amount of time it'll take to travel from point A to point B. > That's something which is very different than Sql.Time, so should it not be > supported? > Who say we are not giving support? Please read from the beginning, the point is: TimeSpan NHibernate type was moved to TimeSpanInt64. > It seems like the goal should be able to take a value, save it, load it > back and still have the same value, regardless of what the common usage is. > There are plenty of applications that use it correctly, but in a different > way. > Yes, that's why in the release notes it's said in the breaking change stuff. -- 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 -~----------~----~----~----~------~----~------~--~---
