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=
UC
On Wednesday 01 November 2006 13:15, pgsql-general@list.coretech.ro wrote:
> hello,
>
> can the the current time family functions (CURRENT_TIMESTAMP, LOCALTIME,
> etc) reach the '24:00:00' value ?
>
> I want to compare LOCALTIME <= '24:00:00'::TIME and I am curios to know
> if LOCALTIME < '24:00:00'::TIME is sufficient.
>
>
> thanks,
> razvan radu
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
--
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
