| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Euler Taveira de Oliveira" <euler(at)timbira(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: wrong behavior using to_char() |
| Date: | 2006-09-14 22:52:36 |
| Message-ID: | 16678.1158274356@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
"Euler Taveira de Oliveira" <euler(at)timbira(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-09-14 22:55:17 | Re: wrong behavior using to_char() |
| Previous Message | Bruce Momjian | 2006-09-14 20:11:56 | Re: pgsql on Solaris 10 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-09-14 22:55:17 | Re: wrong behavior using to_char() |
| Previous Message | Euler Taveira de Oliveira | 2006-09-14 19:54:00 | wrong behavior using to_char() |