| From: | Zdeněk Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Subject: | Re: lc_time and localized dates |
| Date: | 2008-02-28 11:54:11 |
| Message-ID: | 47C6A0E3.8080306@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut napsal(a):
> Am Dienstag, 26. Februar 2008 schrieb Zdenek Kotala:
>
>> But how you handle situation when you have multi language application
>> which needs correct output for all languages? You cannot use any of the
>> pattern because it will be wrong for some group of languages.
>>
>
> This is what you get when you copy a proprietary, poorly specified interface.
> The to_char functions are supposed to be Oracle-compatible, so we need to
> check what Oracle does. Whether that is useful in practice is a bit
> secondary.
>
I see. It is ok from this point of view.
> I'm beginning to think, if you want formatting functions that are more sane,
> stable, and standardized, export sprintf and strftime to PostgreSQL
Yes, it should solve a problem.
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-02-28 12:40:16 | Re: Logging conflicted queries on deadlocks |
| Previous Message | ITAGAKI Takahiro | 2008-02-28 08:46:04 | Logging conflicted queries on deadlocks |