From: | "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, "pgsql-general(at)list(dot)coretech(dot)ro" <pgsql-general(at)list(dot)coretech(dot)ro> |
Subject: | Re: time value '24:00:00' |
Date: | 2006-11-02 08:54:38 |
Message-ID: | 200611020054.38451.uwe@oss4u.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 02 November 2006 00:16, Richard Huxton wrote:
> Uwe C. Schroeder wrote:
> > why don't you just use < '00:00:00'::time
> > and avoid the issue?
> >
> > IMHO there shouldn't even be a 24:00:00, because that would imply that
> > there is a 24:00:01 - which there is not.
> > It should go from 23:59 to 00:00
> > But then, I didn't write the spec for time in general, so maybe there is
> > a 24:00 which is identical to 00:00
>
> Ah, times and dates are wonderful things though. For example, '23:59:60'
> is a valid time (and not equal to 24:00:00 or 00:00:00) every so often.
>
> http://en.wikipedia.org/wiki/Leap_second
Yeah, but isn't the third part milliseconds? Doesn't "milli" imply 1000 and
not 60. I may be totally off here though - well, it's getting late
UC
--
Open Source Solutions 4U, LLC 1618 Kelly St
Phone: +1 707 568 3056 Santa Rosa, CA 95401
Cell: +1 650 302 2405 United States
Fax: +1 707 568 6416
From | Date | Subject | |
---|---|---|---|
Next Message | Hari Bhaskaran | 2006-11-02 08:57:08 | Availability of pg_backend_pid() immediately after connection establishment |
Previous Message | Richard Huxton | 2006-11-02 08:16:29 | Re: time value '24:00:00' |