Jorge Godoy wrote:
> > In the pt_BR locale, the thousand separator is "". So it should return
>
> The thousands separator in pt_BR is ".".
>
Oh, good catch. There is so much hack in my glibc. :-)
--
Euler Taveira de Oliveira
http://www.timbira.com/
---(end of b
Bruce Momjian wrote:
> One idea would be to handle C locale behavior differently from non-C
> locale.
Right.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom Lane wrote:
> "Euler Taveira de Oliveira" <[EMAIL PROTECTED]> writes:
> > In the pt_BR locale, the thousand separator is "". So it should return
> > 12345,670. Looking at the source, I saw that the test cases for locale
> > properties are independent among them. I think that the correct form is
"Euler Taveira de Oliveira" <[EMAIL PROTECTED]> writes:
> In the pt_BR locale, the thousand separator is "". So it should return
> 12345,670. Looking at the source, I saw that the test cases for locale
> properties are independent among them. I think that the correct form is to
> have all-or-nothin
Hi,
I notice a strange behavior using to_char() function. I'm using locale
pt_BR but it could happen with any locale.
template1=# select to_char(12345.67, '999G999D999');
to_char
--
12,345,670
(1 registro)
In the pt_BR locale, the thousand separator is "". So it should return
Based on the date of the posting, I think this will be fixed when we
release 8.1.5 soon. If you want, use CVS to pull the 8_1 tag and try
that.
---
[EMAIL PROTECTED] wrote:
> Compiling PostgreSQL 8.1.4 under Solaris 10, I r
