On Sun, 2005-03-27 at 12:03 +0200, Karel Zak wrote:
> On Sat, 2005-03-26 at 15:56 -0800, Josh Berkus wrote:
> > Alvaro,
> >
> > > On Sat, Mar 26, 2005 at 02:04:14PM -0800, Josh Berkus wrote:
> > > > SELECT to_char( INTERVAL '43 hours 20 minutes', 'MI' ) || ' min';
> > > > 2600 min
> > >
> > > Hmm, what if you wanted more than one literal string? Say "1 mon 3
> > > days" ... your concatenation idea wouldn't work. ISTM the format string
> > > should allow unconverted literals, so you would use
> > >
> > > SELECT to_char( INTERVAL '43 hours 20 minutes', 'MI min' );
>
> Well, I'm going to check how difficult will be implement correct to_char
> (interval).
Hmm, if we want to support conversion like:
'43 hours 20 minutes' --> 'MI min'
how we should work with calendar INTERVAL units? For example 'month'?
'1 month 1 day' --> 'D days'
I think answer should be error message: "missing calendar unit 'month'
in output format"
Karel
--
Karel Zak <[EMAIL PROTECTED]>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
