Added to TODO:

   * Add GUC variable to allow output of interval values in ISO8601 format


Tom Lane wrote:
> Ron Mayer <[EMAIL PROTECTED]> writes:
> >   Would formatting functions for intervals such as...
> >    to_iso8601basic_char(interval)  -- return ISO-8601 basic fmt interval
> >    to_iso8601basic_char(timestamp) -- return ISO-8601 basic fmt date/time
> >   would be better than a new GUC variable?
> I could see arguments for both --- in the timestamp world we have
> DateStyle to control the default output format, plus to_char when you
> want something different.  I'd suggest continuing with your plan of
> providing GUC control over the default interval format (just use a
> separate GUC variable, please, for orthogonality).  If you want to add
> an explicit formatting function later, you can do that too.
> BTW, I do not recall exactly why Karel wants to deprecate
> to_char(interval), but I don't think it's because of any fundamental
> objection to the notion of a formatting function.  I think it was
> because the present definition is badly designed and needs to be
> replaced with a different API.
>                       regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Reply via email to