From: | "Nick Addington" <adding(at)math(dot)wisc(dot)edu> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2056: to_char no long takes time as input? |
Date: | 2005-11-20 07:53:50 |
Message-ID: | 20051120075350.5FEDCF0B25@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
The following bug has been logged online:
Bug reference: 2056
Logged by: Nick Addington
Email address: adding(at)math(dot)wisc(dot)edu
PostgreSQL version: 8.1.0
Operating system: aix
Description: to_char no long takes time as input?
Details:
The following code works in 8.0.4 but fails in 8.1.0:
select to_char('1:00 pm'::time,'HH:MM AM');
8.1.0 gives this is the error message:
ERROR: invalid format specification for an interval value
HINT: Intervals are not tied to specific calendar dates.
I saw some discussion on the -hackers list about deprecating
to_char(interval, text), but do you really want to chuck to_char(time,
text)? That's a useful function. Or at least, I was using it...
Please advise,
Nick Addington
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-11-20 09:07:14 | Re: BUG #2056: to_char no long takes time as input? |
Previous Message | kerry | 2005-11-20 02:14:20 | password issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-11-20 09:07:14 | Re: BUG #2056: to_char no long takes time as input? |
Previous Message | Alvaro Herrera | 2005-11-19 22:55:15 | Re: DROP OWNED again |