Hi all.I think that we should revert the implementation (breaking change) in
the trunk.
IMO Timespan should be the oldone.

For MsSQL2008 DbType.Time we should implements something specific if there
is a Microsoft "best-practice" where they prefer TimeSpan represented in
a DbType.Time.

In CLR TimeSpan is a time lapse without a limitation inside 24hs.

Opinions ?

Please before Alpha2 (Sunday)
-- 
Fabio Maulo

Reply via email to