Re: BUG #2056: to_char no long takes time as input? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2056: to_char no long takes time as input?
Date
Msg-id 28941.1132505987@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2056: to_char no long takes time as input?  ("Nick Addington" <adding@math.wisc.edu>)
Responses Re: BUG #2056: to_char no long takes time as input?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
"Nick Addington" <adding@math.wisc.edu> writes:
> The following code works in 8.0.4 but fails in 8.1.0:
> select to_char('1:00 pm'::time,'HH:MM AM');

I'm inclined to think that disallowing AM/PM for intervals was a mistake
--- if we allow both HH and HH24 (which we do) then the various flavors
of AM/PM seem reasonable to allow as well.

Bruce, did you have a specific rationale for that?

I notice the code now specifically forces HH to be treated as HH24 in
the interval case, which was not so before 8.1; we would need to revert
that change as well to continue supporting TIME cases reasonably.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Martin Pitt
Date:
Subject: Fwd: Bug#338645: postgresql-contrib-8.1: dbf2pg silently ignores the -F and -T options
Next
From: Tom Lane
Date:
Subject: Re: postgresql8.1 crushes on some inserts/updates in KOI8 encoding