From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
Subject: | Re: Question about Postgresql time fields(possible bug) |
Date: | 2006-01-10 21:14:31 |
Message-ID: | 200601101314.32227.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tony, Dave,
> That's not really the point. The ISO 8601 standard allows midnight to be
> expressed as 00:00:00 or 24:00:00 to enable you to tell which midnight
> is being referred to (ie. The beginning or the end of the day).
IIRC, the reason for supporting 24:00:00 is that some popular client
languages (including PHP, I think) use this number to express "midnight".
I personally also find it a useful way to distinguish between "blank
time" (00:00) an "specifically intentionally midnight" (24:00).
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2006-01-10 22:00:02 | Re: Improving N-Distinct estimation by ANALYZE |
Previous Message | Tom Lane | 2006-01-10 21:12:17 | Re: Question about Postgresql time fields(possible bug) |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-01-10 22:41:04 | TupleDesc refcounting |
Previous Message | Tom Lane | 2006-01-10 21:12:17 | Re: Question about Postgresql time fields(possible bug) |