| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Euler Taveira <euler(at)timbira(dot)com(dot)br>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Inconsistency between TO_CHAR() and TO_NUMBER() |
| Date: | 2013-05-13 14:09:18 |
| Message-ID: | 2768.1368454158@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-05-13 14:24:55 | Re: BUG #8154: pg_dump throws error beacause of field called "new". |
| Previous Message | willybas | 2013-05-13 14:00:16 | BUG #8154: pg_dump throws error beacause of field called "new". |