Re: Bug in docs - modifiers for to_char()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: depesz(at)depesz(dot)com
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug in docs - modifiers for to_char()
Date: 2015-06-25 14:36:35
Message-ID: 1876.1435242995@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> in Table 9-23
> (http://www.postgresql.org/docs/devel/static/functions-formatting.html)
> It says:
>> FM prefix | fill mode (suppress padding blanks and trailing zeroes)
> In next part it says:
>> FM suppresses leading zeroes and trailing blanks
> From all I can tell, the text in table is wrong - wasn't able to find
> any case where FM would delete trailing zeros, and it definitely removes
> leading ones.

Yeah, you're right.

I also fail to find anyplace where it explains what FM does for input
cases. However, to_number/to_date/to_timestamp are woefully
underdocumented anyhow (eg, almost no examples), so maybe that would
be better addressed as part of a larger rewrite.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message brsaweda 2015-06-25 19:24:03 BUG #13469: Systematic typo in dblink documentation
Previous Message Marko Tiikkaja 2015-06-25 13:05:47 Re: BUG #13465: multi update query use CTE, result & plan not equal, BUG?