From: | "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> |
---|---|
To: | "Hiroshi Inoue" <inoue(at)tpf(dot)co(dot)jp>, "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Solve a problem of LC_TIME of windows. |
Date: | 2009-01-07 16:44:31 |
Message-ID: | 2E57409AFBEF4D42ADC8763A76DF1891@HIRO57887DE653 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> I've also thought a similar implementation but there seems
> a problem of efficiency.
> As far as I see wcsftime() is almost = strftime() + mbstowcs()
> and so using strftime() is effective at least for the following
> cases.
>
> 1) LC_CTIME is "C".
> 2) LC_CTYPE != C and the database encoding != UTF-8. In this
> case the current restriction of PostgreSQL requires that
> the database encoding matches the encoding of the LC_CTYPE.
>
> We seem to be able to call strftime() directly in above cases.
>
> Comments ?
I quite agree on that point.
==
遅くまですみません、、もう寝ましょう:-)
Regards,
Hiroshi Saito
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-01-07 16:53:04 | Re: Multiplexing SUGUSR1 |
Previous Message | Tom Lane | 2009-01-07 16:44:19 | Re: float8 strtod weirdness |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2009-01-07 21:47:38 | Re: Solve a problem of LC_TIME of windows. |
Previous Message | Hiroshi Inoue | 2009-01-07 16:37:22 | Re: Solve a problem of LC_TIME of windows. |