Re: Why length(to_char(1::integer, '9')) = 2 ? - Mailing list pgsql-general

From Dmitriy Igrishin
Subject Re: Why length(to_char(1::integer, '9')) = 2 ?
Date
Msg-id AANLkTikP=t2hoq36TTS3Zx7mF7CzDivseUM6Y_tjbNYD@mail.gmail.com
Whole thread Raw
In response to Re: Why length(to_char(1::integer, '9')) = 2 ?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Why length(to_char(1::integer, '9')) = 2 ?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general


2011/3/10 Bruce Momjian <bruce@momjian.us>
Dmitriy Igrishin wrote:
> dmitigr=> SELECT '>'||to_char(0.1, '0.99999')||'<' AS v;
>      v
> ------------
>  > 0.10000<
>
> dmitigr=> SELECT '>'||to_char(0.1, 'FM0.99999')||'<' AS v;
>    v
> -------
>  >0.1<
>
> So, padding zeroes suppressed by FM is a rest of the value.

Any documentation changes suggested?
I propose to replace "fill mode (suppress padding blanks and zeroes)"
located here
http://www.postgresql.org/docs/9.0/static/functions-formatting.html#FUNCTIONS-FORMATTING-NUMERICMOD-TABLE
with
"fill mode (suppress padding blanks and trailing zeroes)".

--
 Bruce Momjian  <bruce@momjian.us>        http://momjian.us
 EnterpriseDB                             http://enterprisedb.com

 + It's impossible for everything to be true. +



--
// Dmitriy.


pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Why length(to_char(1::integer, '9')) = 2 ?
Next
From: Bruce Momjian
Date:
Subject: Re: Upgraded to 9.0.3, No Man Pages