Re: BUG #15091: to_number() returns incorrect value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: michael(dot)aiello(at)asg(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15091: to_number() returns incorrect value
Date: 2018-02-26 17:48:29
Message-ID: 27576.1519667309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> When to_number is called with a string that contains a decimal point, but
> there is no decimal indicator in the format string, the decimal digits are
> appended to the integer portion, having the effect of increasing the the
> integer value.
> This can be reproduced with a simple SELECT, as follows:

> SELECT to_number('123.0', 'FM9999999');
> returns value 1230

[ experiments ... ] I get the same result on Oracle, so I'd say this
is the "correct" behavior.

> by comparison, a decimal indicator in the format returns the correct
> value:

> SELECT to_number('123.0', 'FM99999D999');
> returns 123.0

On the other hand, Oracle also returns 1230 for this case :-(.
But that seems to be a locale issue --- if I change the D to "."
I get the expected result 123.

Tested at
http://rextester.com/l/oracle_online_compiler

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jonathan Allen 2018-02-26 18:28:12 RE: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Previous Message TipTop Labs 2018-02-26 16:28:53 Re: BUG #14999: pg_rewind corrupts control file global/pg_control