Re: wrong behavior using to_char() - Mailing list pgsql-bugs

From Tom Lane
Subject Re: wrong behavior using to_char()
Date
Msg-id 16678.1158274356@sss.pgh.pa.us
Whole thread Raw
In response to wrong behavior using to_char()  ("Euler Taveira de Oliveira" <euler@timbira.com>)
Responses Re: wrong behavior using to_char()
List pgsql-bugs
"Euler Taveira de Oliveira" <euler@timbira.com> 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-nothing test case or didn't test *lconv->property ("" is
> evaluated to false). Attached is a patch that fixes it using the second
> option.

Not unless you have a solution to the problem seen in this thread:
http://archives.postgresql.org/pgsql-patches/2006-02/msg00172.php

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Euler Taveira de Oliveira"
Date:
Subject: wrong behavior using to_char()
Next
From: Bruce Momjian
Date:
Subject: Re: wrong behavior using to_char()