| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: to_char issue? |
| Date: | 2009-09-28 15:11:13 |
| Message-ID: | 943.1254150673@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dave Page <dpage(at)pgadmin(dot)org> writes:
> This was posted as a documentation comment:
> to_char(interval '0d 0h 12m 44s', 'DD HH MI SS');
> with HH and HH12 will return 12 instead of 0.
> Testing on 8.4.1, it does seem to be the case that you get "00 12 12
> 44". Seems bogus to me, but am I and the OP missing something?
Hmm ... it would be expected in the case of a timestamp, but seems
wrong when the input is interval. You do get sane behavior from
HH24. I guess the question is whether there is any use in different
behavior between HH12 and HH24 for intervals.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-28 15:15:38 | Re: BUG #5081: ON INSERT rule does not work correctly |
| Previous Message | Heikki Linnakangas | 2009-09-28 15:10:07 | Re: BUG #5084: Query gives different number of rows depending on ORDER BY |