| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Inconsistency between TO_CHAR() and TO_NUMBER() |
| Date: | 2013-05-10 16:09:58 |
| Message-ID: | kmj64d$qrq$1@ger.gmane.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote on 10.05.2013 17:49:
> I looked into this, and find that the reason it misbehaves is that
> NUM_numpart_from_char() will treat a '.' as being a decimal point
> *without any regard to locale considerations*. So even if we have
> a locale-dependent format string and a locale that says '.' is a
> thousands separator, it does the wrong thing.
>
> It's a bit surprising nobody's complained of this before.
>
> I propose the attached patch. I'm slightly worried though about whether
> this might break any existing applications that are (incorrectly)
> depending on a D format specifier being able to match '.' regardless of
> locale. Perhaps we should only apply this to HEAD and not back-patch?
The manual claims that 'D' is locale dependent (whereas '.' is not), so
_theoretically_ a back patch would make sense I guess.
--
Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Roller | 2013-05-10 20:41:49 | Re: BUG #8143: Backend segmentation fault in pg_trgm |
| Previous Message | Tom Lane | 2013-05-10 15:49:18 | Re: Inconsistency between TO_CHAR() and TO_NUMBER() |