On Sep 1, 2006, at 9:12 , Tom Lane wrote:
Michael Glaesemann <[EMAIL PROTECTED]> writes:
I came across some behavior that seems counterintuitive to me:
test=# select '1.5 mon'::interval;
interval
-----------------
1 mon 360:00:00
(1 row)
With the time/day/month interval struct introduced in 8.1, I'd expect
this to return '1 mon 15 days'. The reason is that the DecodeInterval
converts fractional months to time directly, rather than cascading
first to days.
I agree that this seems like an oversight in the original
months/days/seconds patch, rather than behavior we want to keep.
But is DecodeInterval the only place with the problem? My
recollection
is that there's a certain amount of redundancy in the datetime
code ...
I'll check on this tonight. Any idea where I might start to look?
Michael Glaesemann
grzm seespotcode net
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
