From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
Cc: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: '1 year' = '360 days' ???? |
Date: | 2004-10-24 15:29:13 |
Message-ID: | 8917.1098631753@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Glaesemann <grzm(at)myrealbox(dot)com> writes:
> Added to this, I've been wondering whether '1 day'::interval is also
> problematic wrt daylight savings time or changing time zones.
This is exactly the point I alluded to earlier: intervals need to have
three components (months, days, seconds) not just two. That's been on
the to-do list for quite awhile. All the other units we support for
intervals bear a fixed relationship to one or another of these, so
three is sufficient.
Question to think about: should we allow fractional months or days in
the stored representation? There are some places where the existing
restriction that the months field is an integer requires awkward
compromises. On the other hand, it's not real clear what a fractional
month actually means, and similarly a fractional day is hard to assign
meaning to without positing that 1 day == 24 hours.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-10-24 16:17:49 | Re: '1 year' = '360 days' ???? |
Previous Message | Francisco | 2004-10-24 15:14:58 | Permission denied error |