Re: Potential to_char localization bug

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Potential to_char localization bug
Date: 2006-11-27 14:45:59
Message-ID: 20061127144559.GF4432@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> Here is a localization bug waiting to happen:
>
> static char *
> localize_month_full(int index)
> {
> char *m = NULL;
>
> switch (index)
> {
> case 4:
> m = _("May");
> break;
>
>
> static char *
> localize_month(int index)
> {
> char *m = NULL;
>
> switch (index)
> {
> case 4:
> m = _("May");
> break;
>
>
> Haven't thought of a fix yet.

Build a table/function to return short names for full month names, and
use full-length month names on localize_month?

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-11-27 15:03:50 Re: tiny fix needed
Previous Message Andrew Sullivan 2006-11-27 14:42:01 Re: Incrementing INET fields