SCM

[#1003336] Partial support for Interval/TimeSpan type

View Trackers | Patches | Download .csv | Monitor

Date:
2007-04-20 13:46
Priority:
3
State:
Open
Submitted by:
Nobody
Assigned to:
Nobody (None)
Category:
Group:
Resolution:
None
 
Summary:
Partial support for Interval/TimeSpan type

Detailed description
Append partial suuport for interval data type.
Support for 'years' and 'months' missing.

Followup

Message
Date: 2009-01-16 13:29
Sender: Jon Hanna

I can't see what you mean about support for months being missing. It is part of ToString(), Parse() and explicitly returned by Months.

Years would be problematic in that since we already treat months separate to days (to duplicate PostgreSQL behaviour) so while one user may wish to have Months/12 another may wish to have Months/12 + days/365.25 and another Months/12 + Days/365.25 + TotalHours/8766.0. PostgreSQL behaviour like the first and TimeSpan has no equivalent behaviour, which would suggest the first as the best, but this is far from clear and undoubtedly the right choice for some would be wrong for others. Best to let them decide themselves.

Attached Files:

Changes:

No Changes Have Been Made to This Item

Powered By FusionForge