| From: | Ted Nolan SRI Augusta GA <ted(at)ags(dot)ga(dot)erg(dot)sri(dot)com> |
|---|---|
| To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dale Anderson <danderso(at)crystalsugar(dot)com>, pgsql-general(at)postgresql(dot)org, ted(at)ags(dot)ga(dot)erg(dot)sri(dot)com |
| Subject: | Re: DateTime fields |
| Date: | 2000-06-28 16:25:32 |
| Message-ID: | 200006281625.MAA00858@ags.ga.erg.sri.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In message <Pine(dot)LNX(dot)3(dot)96(dot)1000627094243(dot)5765A-100000(at)ara(dot)zf(dot)jcu(dot)cz>you write:
>
>On Mon, 26 Jun 2000, Tom Lane wrote:
>
>> "Dale Anderson" <danderso(at)crystalsugar(dot)com> writes:
>> > I noticed that the DateTime fields and the to_timestamp function
>> > interpret 12 PM as 00:00 and 12 AM as 12:00.
>>
>> Huh?
>>
>> Looks fine to me.
>
>No, you overlook "to_timestamp()" in query. This routine really has bug in
>PM/AM interpretation.
>
> Karel
>
Just wanted to point out that there was a court case (involving "no
parking" signs with confusing hours) several years ago that established
that, for at least parts of the US, 12 Noon is legally neither AM nor
PM. This actually makes logical sense as well,
AM is "ante meridiem", ie "before noon"
and
PM is "post meridiem", ie "after noon"
so noon itself can be neither.
Ted Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur M. Kang | 2000-06-28 16:32:29 | Lingering Backend Processes |
| Previous Message | Tom Lane | 2000-06-28 16:20:44 | Re: Trigger (C) question |