Re: BUG #2056: to_char no long takes time as input?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Nick Addington <adding(at)math(dot)wisc(dot)edu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2056: to_char no long takes time as input?
Date: 2005-12-02 04:06:50
Message-ID: 27565.1133496410@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Oh, one more thing. With the new patch I just posted, '0 hours' and
> 'HH' returns 12:

> test=> select to_char('0 hours'::interval, 'HH');
> to_char
> ---------
> 12
> (1 row)

Yeah, it's done that in every release since 7.2. 8.1.0 is the only
release that thinks 00 is correct.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-12-02 05:29:10 Re: BUG #2087: Bogus error message on CREATE TRIGGER with a SQL function
Previous Message Bruce Momjian 2005-12-02 04:02:38 Re: BUG #2056: to_char no long takes time as input?

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-12-02 04:34:00 Re: Numeric 508 datatype
Previous Message Tom Lane 2005-12-02 04:03:52 Re: [HACKERS] Should libedit be preferred to libreadline?