From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: unexpected character used as group separator by to_char |
Date: | 2021-03-09 21:32:20 |
Message-ID: | f4135958-86f4-b68d-5315-bcc6d38c032d@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/9/21 2:22 PM, Tom Lane wrote:
> Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> writes:
>> Having a database with the proper lc_numeric setting for each country, and using to_char/to_number to manipulate numbers is much more appealing than writing my own parser in my front end. But this weird space is getting in my way.
> The point here is that 'G' and related format codes act as specified by
> your LC_MONETARY locale. If you don't like the results, you need to use
> a different locale.
>
> (I suppose you could also use regexp_replace to convert random forms
> of whitespace to plain ASCII space.)
>
> regards, tom lane
>
>
I'm in David's camp on this one: there are plenty of currency format
conversion libraries from which to choose.
rjs
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-03-09 22:16:11 | Re: Need help with clarification on stored procedure support in PostGreSQL database |
Previous Message | Tom Lane | 2021-03-09 21:22:07 | Re: unexpected character used as group separator by to_char |