Re: Inconsistency between TO_CHAR() and TO_NUMBER() - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Inconsistency between TO_CHAR() and TO_NUMBER()
Date
Msg-id 2768.1368454158@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inconsistency between TO_CHAR() and TO_NUMBER()  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Inconsistency between TO_CHAR() and TO_NUMBER()  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-bugs
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> Would it be possible to be lenient, and also accept . as the decimal
> separator, when there is no ambiguity? Ie. when . is not the thousands
> separator.

I originally coded it that way, but concluded that it was probably a
waste of code space.  How many locales can you point to where neither
the decimal point nor thousands_sep is "."?  It certainly wouldn't be
enough to noticeably reduce the potential pain from this change, so
I decided that it'd be better to keep the behavior straightforward
and as-documented.

            regards, tom lane

pgsql-bugs by date:

Previous
From: willybas@gmail.com
Date:
Subject: BUG #8154: pg_dump throws error beacause of field called "new".
Next
From: Tom Lane
Date:
Subject: Re: BUG #8154: pg_dump throws error beacause of field called "new".