Hi all. I agree with Oskar, Roger and Jay. Timespan is conceptually a duration (time interval), not a time. We use it to express "age" like 1h, 24h, 7days, 1month etc. Using it as a time is a very special case that should be explicit. After all because it reduces the value range massively. You wouldn't map an integer to a byte by default, would you?
On Mar 25, 10:28 pm, Oskar Berggren <oskar.bergg...@gmail.com> wrote: > Thanks Dario for you clarification above. > > I have created issue NH-1716 to request that the default remain as the old > behaviour. > > A few additional notes: > > One could argue that if you are database centric and already have a column > of type TIME it is not entirely unreasonable to handle this as a TimeSpan in > an application, since MS didn't bother to create a "System.Time" at the same > time they did the System.DateTimeOffset. > > However, if you are domain model centric and use TimeSpan because you really > want to, the most reasonable default persisting of this should be the one > least limiting. > > And the default in NHibernate should be to best support the domain model > approach right? > > Regards, > Oskar > > 2009/3/25 Dario Quintana <conta...@darioquintana.com.ar> > > > To @Roger and @Jay: > > > I don't have complains to vote for "who" is the default. We were asking to > > the community for that, the point was that we got any answer. > > > But "who is default" is another issue in the Jira. > > > Cheers. > > -- > > Dario Quintana --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
