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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Cc: michael(dot)aiello(at)asg(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15091: to_number() returns incorrect value
Date: 2018-02-26 20:31:49
Message-ID: 8870.1519677109@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Tom> Tested at
> Tom> http://rextester.com/l/oracle_online_compiler

> The problem is that this tester is defaulting to a German locale and
> using . as a thousands separator and , as decimal point, as shown by
> this query:
> select * from nls_session_parameters
> where parameter in ('NLS_TERRITORY','NLS_NUMERIC_CHARACTERS')

Oh, thanks ... I was wondering what locale it had chosen, but did
not know how to find out.

> If you do
> ALTER SESSION SET NLS_TERRITORY = 'AMERICA' \\
> SELECT to_number('123.0', 'FM9999999') FROM DUAL
> then the result is, as expected,
> ORA-01722: invalid number

Hmm. That doesn't seem too helpful. Between throwing an error
and returning "123", seems like the latter would be better.
Do we want to be bug-compatible here?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2018-02-26 20:46:28 Re: BUG #15091: to_number() returns incorrect value
Previous Message Andrew Gierth 2018-02-26 20:25:55 Re: BUG #15091: to_number() returns incorrect value