From: | "Christopher Browne" <cbbrowne(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: time value '24:00:00' |
Date: | 2006-11-02 13:32:08 |
Message-ID: | d6d6637f0611020532r12bca21avd5dc64c9bd549ea6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/1/06, Uwe C. Schroeder <uwe(at)oss4u(dot)com> 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:0
Keep in mind the times when there is an extra leap second added in. I
suspect that in those cases, we get "23:60"; that seems actually a
little bit stranger than 24:00...
--
http://www3.sympatico.ca/cbbrowne/linux.html
Oddly enough, this is completely standard behaviour for shells. This
is a roundabout way of saying `don't use combined chains of `&&'s and
`||'s unless you think Gödel's theorem is for sissies'.
From | Date | Subject | |
---|---|---|---|
Next Message | Hitoshi Harada | 2006-11-02 13:53:52 | compiling c-function on various version |
Previous Message | Peter | 2006-11-02 11:35:41 | Weird double single quote issue |